Skip to main content
J
jg1231
Participating Frequently
February 17, 2016

P: Low Performance when there are a lot of artboards

  • February 17, 2016
  • 16 replies
  • 2224 views

When there are a lot of artboards in one PS document, after a while the application becomes really slow. E.g.:

- when selecting layers it sometimes freezes for a few seconds.

- applying paragraph styles is pain in the ass, as every change renders for at least 10 seconds before displaying the change. Interestingly when the text is marked directly in the text field, applying paragraph styles is lightning-fast!

- saving takes almost forever, even when the file is only 150 Mb

- also PS seems to use less RAM than it could. System has 20Gb free RAM and PS seems to write on the working volume...

---

Photoshop CC Version 2015.1.2

---

My System:

ThinkPad P70
Intel Xeon E3 1505M
Quadro M5000M, 8Gb RAM
32Gb RAM
PCIe Drive

    This topic has been closed for replies.

    16 replies

    J
    J453
    Legend
    June 21, 2016
    This issue should be much better in the CC 2015.5 upgrade released today: https://blogs.adobe.com/photoshop/2016/06/adobe-releases-major-photoshop-cc-update-today-and-announces-more-digital-imaging-product-features-coming-soon.html
      J
      jg1231Author
      Participating Frequently
      April 6, 2016
      Chris, that's really great that you found a fix to the issue! Will improve working a lot 🙂 Looking forward to the release & hope it will not take too long 😉
      Thanks for your efforts!
      F
      FeedbackCommunityMember
      Inspiring
      April 5, 2016
      It will be in the next major release. We can't say what that release might be called.
      F
      FeedbackCommunityMember
      Inspiring
      April 5, 2016
      So is this fix is present in CC2015.x or it will be in CC2016 ?
      F
      FeedbackCommunityMember
      Inspiring
      March 22, 2016
      Good news:  what I found was the cause of the slowdown, and my fix solved it.

      The fix will be in the next major release of Photoshop. It needs a lot of testing, because I just changed the way all text renders in Photoshop (not the appearance, but the underlying mechanism to do the rendering - oh, boy did that scare some QE and managers).

      After my fix, the remaining time is all spent rendering the actual text, and manipulating the text data structures (i.e.:  work that can't be avoided).  I've got a few ideas to make things a little better in the future, but they require large scale refactoring of the text code (make the data structures more efficient) and will take a lot more work and testing.
      J
      jg1231Author
      Participating Frequently
      February 22, 2016
      Chris, that's great! Hope it gets fixed, so working with text will be as pleasant as in InDesign 🙂 Thanks for your efforts!
      F
      FeedbackCommunityMember
      Inspiring
      February 19, 2016
      OK, I think I found the cause of the slowdown.
      Basically some of the type layers are re-rendering across the entire document (all 13.3k x 9.6k of it) instead of limiting themselves to the actual area of the text.  So this will get slower as you make the document larger by adding more artboards.
      I need to talk to our text engineer and see what we can do about this.
      F
      FeedbackCommunityMember
      Inspiring
      February 19, 2016
      First 8 files done, now looking at yours.

      Moving things on that complex a canvas is slow unless you turn off smart guides.  (I'll look into that later)

      I couldn't get paragraph style changes to take very long, until I changed Headline 80.
      That will hang for about 6 seconds when you change the font, and again after you hit OK.
      Alright, now to profile it.

      1261 layers in your document. And the paragraph change seems to spend all it's time re-rendering type layers.
      J
      jg1231Author
      Participating Frequently
      February 19, 2016
      Hey Chris, 
      thanks a lot for taking a look at it, I really appreciate your efforts! Don't worry if you don't find the time today 🙂 Looking forward to your suggestions!
      F
      FeedbackCommunityMember
      Inspiring
      February 19, 2016
      Cache levels and tile size depend a lot on the type of document you are working with.
      Unless you have HUGE documents, you probably want 3 or 4 cache levels.
      The tile size is harder to explain.  Filtering runs faster with large tiles, while file IO works faster with small tiles. And, of course, Your Mileage May Vary.

      Yes, I agree performance shouldn't be that bad - which is why I spend a LOT of time profiling problem areas, finding the cause of the slowdowns, and fixing them (and occasionally educating others on appropriate use of algorithms and data structures).

      I've just been given a flood of problem files to examine, but hopefully I can get to yours sometime today.
      Show more replies
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices