Explore related tutorials & articles
404
Replies
The next pic is a tall one, as I resized the graph to be tall so it would blow up
the "low end" where photoshop is (of usage!)...
A "Bad" feature of the software on the CPU/GPU is that it follows the 'Windows Way' method of reporting CPU/GPU as % of total CPU's/GPU's and has no option to display the considerably more helpful Irix-Unix (who was among the first to have need for showing multiple cpu unit) value of (%/CPU's-summed).
With the CPU, visually, it doesn't make that much difference, but with the GPU, you have to configure the tool to know how many units of the 'CL' units your graphics card has, are used for GPU. In the Nvidia, the HW that powers their 3d graphics overlaps with the HW that can be used when using card as a computation resource. But not all of those computation units can be used for GPU usage.
At the bottom of the pic on my display, I have a button called Nodes... If I click on that
it displays individual graphs for each computation node. You have to manually select
which nodes are used for GPU computation on that graph to get a correct display (lame, but it's a general purpose tool that is HW blind and shows Net/Disk/Mem/CPU/ and a bunch of process details you can't get out of any other single tool. On my system, though, Only 2/14 of the boxes on that computation graph are checked. The result being that
my GPU graph would display 1/14th as high and would never see more than about 7% GPU usage if the GPU's were operating at full tilt in 'default'. Only when configured to show the actual GPU's it can use do I see much on the GPU usage graph.
The mem graph is much less complicated, though it may be representative of how it can be used when using both GPU's to render -- in that it only shows the full memory on 1 internal GPU (1.5G), rather than 3G. It may be that you can only use 3G when you use
it as computation mode memory, and as video mode memory, the regions of multiple GPU's mirror each other so each has it's own local copy -- dunno.
But in the graph you can see my startup of Photoshop first thing this morning -- the highest spike on the GPU was @ 12%, but mostly under 3%, I did not much other than
open the file (4.5k² pixels ~ 380GB, ~ 300 layers, maybe 500-800 (total, not additional) if you count each effect on a layer as a separate layer). The memory peaked at 415MB.
Usage including zooming in on an area, and flicking it around a few times...to
generate some GPU usage -- both low-intensity ops.
After the GPU graph (shows GPU%, mem dedicated (on card), and shared (unintersting).
I also include separate graphs for the OS and CPU usage - the CPU usage graph was taken a bit late, the center spike on CPU's 4+5 (numbering from left=0) corresponds about to the GPU spike on the GPu graph...that's when the file was first displayed/read in.
The OS memory usage graph will fill up as I work as more undo/history becomes available in memory, but GPU mem, GPU%, and CPU% don't escalate over time .. except insomuch as CPU% usage goes up as it becomes busier managing tmp space (The tmp file for working on this file will easily hit 100G if I do too much in one session),
which is when I run out of disk on a 400GB System SSD disk and whine about there being 50GB free on my page-partition, which I keep separate from main HD storage.
OK, I found this thread after waiting seven minutes to try and apply a suface blur to a largish photo in Photoshop CS6. In the end, I gave up, (cancelling didn't work), and quit the program without saving. As suggested by someone early in this thread, I have now switched off the 'use graphic processor' in Preferences, repeated steps I took before with the same image and 'hey presto' all works fine. So my question is, what is my solution and what are the implications of leaving the 'graphic processor' off? I am currently running OS Lion, (fully up to date), on a 27inch Mac. I haven't updated to Mountain Lion yet and I am wondering if this will make any difference?
I'm a photographer not a techy, so answers in plain English would be very much appreciated 
@ Rixie 1 -> update to mountain Lion, so you are shure you've got all the latest drivers etc etc..
Then update to 13.0.1, to be shure you have the latest version of PS CS6,
Install the MAXIMUM of Ram you can install in your computer
Turn off: Time machine, dropbox, ical, mail, safari, any calibration software, icloud sync, any other app's in your launch pad that might be running, menue meters, etc etc..
then put the graphic thing on Basic , ( or Off )
And then, it will run a bit better, but only for a few hours ( like 6) , then you have to close Photoshop, and restart you computer, and then it will run again for aprox 6 h fine..
After using PS CS6 13.0.1 now for Most of the weekend without stopping, ( before i had to use CS5.5 as CS6 before the updat), the conclusion is: "it works ok", not faster not slower, but OK, for a time laps of 6 hours, then it's just like it works itself into a hell of a situation, and doesn't see any way out, so it blocks, so after rebooting it's ok..
I'll test deleting Logs after a few hours, ( well at first keep an eye on them, as i am under the impresison the ASL logs have fun with PS CS6).. see if that helps ..
well what i remarked, is that my SSD is filling up fast when using PS CS6,
So keep an eye on that, Bridge cache, fills realy fast ( 1 day of work on folders of 100 images, ) and it blocks, and in a chain reaction, PS blocks, so i find my self emptying that to..
Further keep an eye on your private/var/log/asl folder, empty it in the morning , and at noon, and in the evening..
You'll see when you're working in PS CS6 it fills up fast to
Mhm, not having loads of time, i discover a bit of at a time what PS CS6 does in caches and library.. so i thing the update is only a hansaplast on a shot woond ... so it bleeds less but it has still problems
From Adobe service, people on this forum form Adobe are realy nice guys, but the official Adobe awnser is: " its your fault, your computer isn't good enough, you need a Lab-setup in zero gravity, and you will see it wil work perfect" ...
hehe
greets
ju
on the other hand, the crop tool is wicked good .. For instance you can make a slection in a ratio , and then crop that just by clicking the tool.. and loads of small workspace improovements, that could make life easier, but mhm, not there yet
To Zebra, it's for mac,
And good idea, to store the caches in each folder, ... never thought to do that ( know it was possible, but i guess i didn't put 2 and 2 together).
i also use Media Pro , a lot , it does read xmp side car ( actually phase one says it's the best way to work with media pro and c1pro)..
Only you have to LOAD the xmp in .. as it's a catalogue software.
But Bridge is in the production easier to work with.. a bit like the GIMP variant, much easier in a retouching workflow..
Mhm, don't have stress about long preview calculating, it takes for ever on a 12core to 
and 8 times out of 10 it doesn't evene make previews of a Tiff with layers..
Personally i have not such a big problem with that..
But thanks for the tips on the cach folder, good idea...
AdChoices