Skip to main content
Charismatic_yogiB82A
Known Participant
May 9, 2012

P: CS6 Slow compared to CS5.1 with large files

  • May 9, 2012
  • 405 replies
  • 5837 views

PS CS6 has a lot of enhancements and great features. it launches very fast, and the control is very responsive and smooth.

although i am experiencing some speed issues with very large files. compared to CS5.1, where i don't have any of these issues.

the files are PSBs, 9000x8000px, 80+layers, RGB, 8bit

i have the same performance settings for both, cs6 and cs5
i am working on MAC PRO, 16GB ram, SSD scratch, 2TB raid, Radeon HD 5770, Snow Leopard.

the main issues i have are:

- no refresh when i move the curve on adjustment layer. the refresh comes after i let go.
- jagged pan
- extremely slow moving of layers and layer groups, even if they are with smaller dimensions (800x400pix)

again, working with files with less layers or smaller dimensions is very fast.

thanks for your help and support!
m.

This topic has been closed for replies.

405 replies

Inspiring
August 15, 2012
You guys are champs for enduring all the slack. if your software wasn't generally so fantastic you wouldn't have such high expectations to keep up with!

it's frustrating when project planning, especially on projects that last months or over a year, sometimes you have to make a software upgrade mid project, and that's when getting off the rails costs money. thanks thogh. hopefully y'all will have this remedied soon.
Inspiring
August 15, 2012
You'll have to ask Apple why the drivers are in such a bad state on MacOS, why they are not updated nearly as frequently as on Windows, and why Apple takes years to distribute the bug fixes they received from the GPU makers.
Inspiring
August 15, 2012
While I was looking around for causes of this problem I saw someone on a forum had written how it was related to us Mac users having poorly written graphics card drivers and this guy was going on about how rock solid his PC Photoshop is.

I find this incredibly frustrating because once upon a time Mac users really were in a minority but now Macs have increased in popularity and market share - (plus wasn't the whole point of OS X that it was a very robust, stable operating system?) - shouldn't the graphics card drivers for Macs be just as good as for PCs?
Inspiring
August 15, 2012
Yes, that reduces the work in generating the thumbnails, and matches the default behavior in previous versions of Photoshop.
But it's still slower than it should be in CS6, which is why we recommend the workaround of turning off the layer thumbnails (which avoids all the work).
Inspiring
August 15, 2012
We have. We've gone to visit people, we've brought people and their machines into the office, we've done dozens of connect sessions.

So far it's either the 2 known causes above, or some external factor (third party plugin, bad font, bad antivirus, old video driver, etc.).

If you have something that is not solved by the workarounds above, we need a LOT more information to reproduce the problem.
Inspiring
August 15, 2012
I fixed the bug related to shape layers. It had a different cause.
Inspiring
August 15, 2012
With all of this angst and obvious challenge - you would think that Adobe would either offer one of their specialists to do a screen share with people experiencing these issues to investigate themselves, or even have some computers shipped to them to demonstrate the issue and get it resolved. This issue is challenging my marriage when work isn't getting completed and tempers are flaring!
Inspiring
August 15, 2012
if it helps you folks troubleshoot, i have noticed that setting the thumbnail contents to "Entire Document" causes less drag than "Layer Bounds"
Inspiring
August 15, 2012
the user in that post shot 2 videos of the same problem: serious lag when moving groups. only difference is that users workaround was hiding the layers palette altogether (same as disabling thumbnail preview). it was never specific to shape layers. same problem. same workaround.
Inspiring
August 15, 2012
It's just a temporary work around.
No, he was able to reproduce a shape layer issue, which was a different problem specific to shape layers (and was already fixed in the final release).