Hey, so far I have been really enjoying CS6 but have noticed one big issue, at least on my machine. Photoshop runs great up until the moment I hit the save button. Then my entire computer crashes to a halt until the save completes (even though I have set photoshop to never use more than 70% of my ram) and once the save is finished everything in photoshop is much slower. Also my entire OS becomes very sluggish which persists until about 10min AFTER i shut down photoshop completely. Even if I close the current document it still continues to struggle which makes me wonder if this is a memory leak in the saving process that holds onto the ram space until the app is shut down?
My computer specs are as follows:
Mac Pro running Lion
2x 2.66 Ghz Zeon CPU
8gb of Ram
1024mb ATI Radeon GPU
250gb 7200rpm startup drive with a pair of 7200rpm 500gb drives in the other bays. (I generally am saving my PSDs to one of these drives)
Gave it a go and didn't see any noticable difference.
One other thing I just thought about is I am almost always opening PSDs though Lightroom. I will do some testing later to see if the problem persists when Lightroom is not active. I'm wondering if maybe it has something to do with Lightroom updating it's preview for high resolution PSDs as they are saved.
There's some kind of mysterious slowness / sluggishness problem with Lightroom / Camera Raw that people have seen on both Mac and PC. I don't know if it's one problem or several... I wonder if it could be affecting you.
It's been seen to make similar powered computers 10+ times different in responsiveness.
A friend of mine uses Lightroom, and he's said it really slows down - to the point where it takes literally 3 seconds for something on the screen to update after changing a control. He hasn't said the problem migrates to Photoshop, but he doesn't actually use Photoshop much.
Do you see the sluggishness in Lightroom, or am I just connecting something that shouldn't be connected here?
See also this thead: http://forums.adobe.com/thread/1036238?tstart=0
Once I save something the whole machine starts running really slow, Lightroom included but until I actually do that Lightroom runs just fine. I will have to do a bit more testing, I wonder if file format has any impact, such as saving as PSD or a multi layer tiff or even a flat jpg. I am really starting to think it has something to do with the connection between Photoshop and Lightroom when I save a multilayer file.
Also I am running a 30" display, not sure if that might impact things?
I doubt it. I have two 20" displays that add up to roughly the same number of pixels as you have, yet don't have the sluggishness issue. And my friend with the sluggishness problem has two smaller displays like I do.
Do you have tools on your Mac that allow you to see what the processor cores are busy with? I wonder if the Save operation kicks something off (like Spotlight indexing) that could be slowing things down.
hmm, so played around a little bit with Activity Monitor and it looks like Photoshop when it saves is duplicating the current open file in memory and then not giving the ram back upon save complete.
Test 1 (small file)
I open file A. Ram usage goes to 900mb.
I create an empty layer in file A and hit save
ram jumps to 1.8gb and stays at 1.8gb until I completely shut photoshop down
Test 2 (large file)
I open file B. Ram usage goes to 2.5gb
I create an empty layer in file B and hit save
ram jumps to 5gb (and stays)
Test 3 (smart object, save and re-open then save again)
I open file B. Ram usage goes to 2.5gb.
I merge all open layers into a new smart object. Ram goes to 5gb.
I hit save and ram goes to 5.2gb.
I close photoshop ram goes back down to 0
I open file B again usage goes to 1gb. (1 smartobject layer must be much more efficient)
I create a new empty layer and save. Ram jumps to 2gb.
(Note when I refer to ram above, I am refering to the amount of ram Activity Monitor is reporting as being used by Photoshop)
Interestingly enough if I create a second empty layer and save again the ram still goes up but only by about 200mb in both cases.
Lightroom seems to be for the most part uneffected mostly sitting at about 900mb. Right when the save completes it bumps up to 1.2gb for a few seconds then right back to 900 (presumably updating the new thumbnail). Also right when the save finishes Lightroom grabs almost my entire CPU power for a few seconds, which likely isn't a big issue, but also worth noting.
Other than Lightroom's little surge CPU stays relatively low the whole time. Photoshop mostly staying under 5%, usually closer to 1%.
I close photoshop ram goes back down to 0
That - Photoshop allocating RAM and not "giving it back" - seems like something to worry about at first, but I can assure you it's designed to work that way. A lot of people discover this behavior and initially think it's a "memory leak".
It may not be quite as well-behaved as we'd like to see with regard to other applications that may need RAM, but Adobe - in the person of Chris Cox - has clearly stated that Photoshop is coded that way on purpose, to provide the best possible performance of Photoshop. Once it's allocated, Photoshop manages it internally itself.
It does that for me too, and I don't see the slowdowns you're experiencing. I'll venture to say most people aren't seeing the sluggishness you've described.
So the mystery to solve is why are you seeing it on your system when some others are not, and possibly a secondary enigma is whether the sluggishness you're seeing could be related to that being seen by some (different) others.
Have you tried experimenting with the tile size/cache levels settings in the Photoshop - Preferences - Performance dialog?
Yes, I have tried playing with the performance, although Photoshop seems to ignore the setting. Or perhaps Activity Monitor is just mis-representing memory usage. Right now I have max Memory usage set in the performance setting to 3.8gb, however, Activity Monitor is reporting photoshop using almost 4.5gb.
I have also tried making my other 2 internal drives additional scratch discs which hasnt done much.
enabling and disabling GPU doesn't have much impact.
Im going to do some tasting with cache levels now to see if that helps