In case I haven't specifically asked in this thread yet, please try the following:
1. Go to performance preferences in Photoshop and change your Advanced GPU settings from Advanced to Basic. Then quit and re-launch the app and see if performance is better.
2. If it isn't with the change, try disabling GPU altogether by unchecking "Use Graphics Processor" in performance preferences. Again, after making this change quit and re-launch PS and see if performance is better.
If both these changes fail to help, let me know and we'll go onto the next set of troubleshooting steps.
I've tried to reproduce your issue on a few systems, even with the same video card and have yet to be able to reproduce the problem. Performance on my systems is about the same or better than CS5 in all cases.
…I cannot remember this Adam asking me to supply anything…
"This Adam" as you call him is Adam Jerugim, one of the Adobe heavyweights.
Oh... by "this" Adam, I did NOT mean to degrade the guy... I just couldnt recall him asking me anything.. Sorry, If I came across as being a punk. NOT my intention...
took less than an hour....;-)
Tried both of your suggestions. And it makes absolutely no difference on two of my systems.
What I did notice though, was that as I did a new portrait today, with about 10 adjustment layers, I had NO issues at all.
Then again, that document was a "baby" in comparison...
What I CAN do is to upload the document in question to my server, you can then download it and see if you have the same issues as I...
let me know if you would like that... And if... Please supply me with your email address.
I also primarily do retouching and every image I work on has a separate adjustment layer for each specific "touch-up". Just eyes for example: irises get a layer, pupils get 2 layers, whites get a layer, the whole eyeball gets a heal/clone layer, the eyelashes get a layer, catchlights get a layer. Then it's on to teeth. A simple portrait will easily have 25 adjustment layers. Typical retouches end up around 100, complex ones can approach 200.
Altonmusic's usage seems very similar to mine, but I haven't seen a significant performance difference from CS5. I am using windows, and per Adobe's advice I just updated my nvidia driver (which annectdotally seemed to help slightly).
That being said. I still see the dodge/burn, healing, blur/smear/sharpen tools get laggier the longer I keep a given instance running. Last night I retouched about a 10 photos. All of them at some point contained at least 20 adjustment layers, as well as maybe 6 smart object/filters. When retouching the 10th photo, the lag between moving the stylis and seeing the change on the screen became too troublesome to continue. Closing and restarting PS solved the problem, but THAT is an issue I didn't have with CS5.
I'm sorry Adam per your request (post 18). I can't seem to be successful recording an action of my worksteps most of which involve the running of actions - my workflow actions seem to fail (errors like "invert layer is not currently available") while I am recording the new one. Probably my lousy job of making actions. I will try again tonight, but is there some specific system data I could capture that would help? I was watching the windows performance monitor last night, and as far as I could see, I never ran out of memory resources - at least 40% were always available. CPU usage was never more than a blip.
Should I move my issue to a new post rather than hijacking Alontmusic's? I am no longer convinced we are having the same problem.
There was another thread specific to slowdowns with tools (Dodge/Burn/etc), but I can't find it for now, so we can work on this here. I have an action that runs Dodge on a large image with tons of layers. I'm trying to reproduce the issue, but it would be worth watching Task Manager to see if Photoshop memory usage continues to climb beyond the limit you've set in performance preferences as you work.
I'm going to keep working with this action for now and will post an update here once I have more info.
Hi Again, All....
Today, I am wearing the hat with the inscription - DUMB AZZ !!!
To all of you reading this here post, Adobe PS CS6 is actually faster than it's predecessor !
I contacted Adam and sent him over the document which I had problems with in CS6.
He guide me in a direction in which I could actually test the speed between CS5.5 & CS6... (Select Timing instead of Document Size in the little flyout menu on bottum left corner)
I.e. Disabling an adj.Layer took 3 seconds in that particular document... in CS6 and 4 Seconds in CS5.5
The reason for the lag... And Adam was the one to figure this one out.... Was that I had a VERY unusual effect of a topic.. 250 Pixels of outer glow...
Disbling this effect took 2.5 seconds off the time of disabling the Adj. Layer... Leaving it almost instaneous....
I have done tests today only to measure the speed of CS5.5 and CS 6 and found that CS6 IS faster than CS5.5.. Hence me with hat saying dumb azz....
Sorry if I have mislead anyone into thinking CS6 is not up to par
A couple updates:
First, I need to give credit to my colleague Mike Shaw for identifying what specifically was slowing down performance in the file - I'll certainly sleep better tonight
Second, I ran an action to try to reproduce the slowdown using tools and wasn't able to - my action ran the Dodge tool 50 times in a row on a single image without any degradation in performance for the entire run. Note that I'm not using a tablet and there might be something about the data being passed there that's slowing down the app (just a WAG). Ted, my email contact info is above so if you'd like to contact me directly I can help you create an action on your system that might help us figure out what's going on.
Well a forehead smacker, but far from dumb azz. A day without a forehead smack is a day without using Photoshop.
Glad you figured it out. Now you realize, I will have to try it to find out what 250 px of outer glow looks like.
Those 250 pixels were a quick way of adding light-integration to a person which I key'ed out of a beige background placing the subject on a golden glowing background.
I should have just duplicated the subject, colored it yellow and gaussian-blurred it... That would have given me the same effect. I will certainly do THAT in the future ;-)
Thanks Adam ...
I will definitely send you an email. Tonight I only did 8 images, but on the last, I began to notice a slow down of the healing brush.
Here is my system info:
i7-2600K CPU @ 3.40 GHz
Windows 7 Home Prem build 6.1.7601
GPU: NVIDIA GTX 550 Ti with 1 GB
NVIDIA Driver: 188.8.131.5210
Wacom Intuous 4
memory for PS 8703 GB (59%)
This memory table I created from the Windows Resource Monitor
Stage: In Use Modified Standby Free
---------- ------------- ------------- ----------- --------
Fresh Start 2070MB 44MB 866MB 13394MB
Start Bridge 2230 64 1179 12863MB
Launch ACR 2780 86 1640 11800
Open 1 smt Obj 5090 112 1833 11333
close 2 images 5775 112 2628 7841 - edited / closed 2 photos, , PS running, no active img
close 1 image 6516 159 3318 6374 - PS running, no active image
close 5 images 6732 247 4543 4843 - PS running, no active image
close PS 2318 108 4613 9327 - PS closed, Br still running
close Br 2090 108 4652 9530
Somehow during the process of launching PS & Br, editing 8 images, and closing PS & Br, free memory was reduced by
just shy of 4GB. The troublesome part is that in use memory increased after each image was closed. Although it wasn't as bad tonight (with only 8 images) by the time I did 12 last night, the tools were noticably sluggish.
Photoshop's "in use" as measured by the OS includes things beyond Photoshop's control (OS buffers, display/UI buffers, the size of the loaded binaries, etc.).
But Photoshop's measured memory use tries to take that into account, and limit actual allocated space to less than you specify in Photohop's preferences.
Allocating the full amount would not make Photoshop sluggish. But if you edit a document larger than RAM and hit the scratch disk a lot - then that could make Photoshop sluggish while it waits for disk IO.
I don't think it's writing to scratch disk frequently. The largest file I was working on last night was only about 760MB and 21 layers. The most "in use" memory reported by windows was 6.7GB and I have 8.7 allocated to PS out of 16GB total installed. But last night, I only noticed a slight increase in sluggishness as opposed to previously when I had opened and closed a dozen or more documents.
What I will do today is just keep running the current instance until the tools become what I would call painfully sluggish - in other words when I would normally shut PS down and start a new instance. What statistics would be useful to you when I reach that state?
hope you're good...
I have found what seems to be a Mac OS X Lion (cant say about Snow Leopard) GUI Bug...
The top of the Photoshop GUI does not flush to the OS X Meny bar...and it is impossible to make it do so..
Just esthetics and you probably already know about it but I thought I would report it, just the same
ScreenShot of BUG =
I have just uninstalled it because I am too busy to deal with the performance issues. After using it for a while, my whole system becomes unusably slow - not just PS6. Also it won't quit completely. I'm used to Adobe programs taking forever to quit - especially Acrobat (???) but PS 6 would never quit --always had to be forced.
For what its worth, I'm working mostly with very large documents - satellite imagery, from a few hundred MB to 2GB. If things calm down here I might try again.