Skip navigation
edho3456321
Currently Being Moderated

Photoshop Latency Issues? when saving....1.5min to open 5.5 min to save same file.

Jan 28, 2013 3:39 AM

I am struggling to optimize my computer for Photoshop.

An example file opens in 85 seconds. Same file saves in 340 seconds.

 

PhotoShop CS6 (13.0.1)

File is 21000 x 21000 - 50 layers (5.8gb .psb saved)

Why so big? - 5k.com/C.jpg

When I open image, I see 2 swap files 67gb & 8.5gb

 

Hard drives

C: Samsung 830 256 ssd boot drive.

Raid0 SSD Samsung 840Pro 256x2 (512total) PSswap/temp (Tests @1100mb/s read @880mb/sec write)(Z77 intel RST v11.0+ raid0 trim)

Samsung 830 ssd media drive (open & save)

File opens in 90 seconds. Saves in 340 seconds.

stays at 0% saved for 270 secs

 

INTEL I7 3770K 3.5G 8M R8 - CPUs utilization - about 12%+- overall - no one cpu above 50%

ASUS SABERTOOTH Z77 lga 1155 MoBo

32gb MEM 8Gx4 GSKILL F3-1866C10Q-32GXL R

 

variables:

tried video card at (Adv, int, basic) no change.

Toyed with an NVIDIA QUADRO 6000 PCI-E 6GB - did not see performance change.

Tried opening&saving to raid0 SSD no change.

switched PSswap & media drives - slowed it down on open & close +- 100sec.

 

I don't understand why it would take so much longer to save than open....

Would a better video card (4gb or 6gb) make a difference?

Would 64gb ram (dif mobo) or 6 core i7-39*0K CPU make a difference?

 

Unrelated - When I pan to bottom-right of image there is a major lag in display. Up to 20 sec. regardless of video settings.

Is there an easy way to calculate video ram needs based on image size? Prefer ATI - was looking at trying v9800 4gb.

Tried NVIDIA QUADRO 6000 PCI-E 6GB - didn't seem better.

 

I recall reading that with SSD drives, having seperate drives for OS, TMP, Media is no longer adventageous....True/False?

 

I am grasping at straws to figure out what my bottlenecks are and how to elliminate them.

 

Thanks in advance for any suggestions/advice.

 

SysInfo

Adobe Photoshop Version: 13.0.1 (13.0.1 20120808.r.519 2012/08/08:21:00:00) x64

Operating System: Windows 7 64-bit

Version: 6.1 Service Pack 1

System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading

Physical processor count: 4

Logical processor count: 8

Processor speed: 3510 MHz

Built-in memory: 32723 MB

Free memory: 5709 MB

Memory available to Photoshop: 29745 MB

Memory used by Photoshop: 84 %

Image tile size: 128K

Image cache levels: 4

OpenGL Drawing: Enabled.

OpenGL Drawing Mode: Basic

OpenGL Allow Normal Mode: True.

OpenGL Allow Advanced Mode: True.

OpenGL Allow Old GPUs: Not Detected.

Video Card Vendor: ATI Technologies Inc.

Video Card Renderer: ATI FirePro V8800 (FireGL)

Display: 2

Display Bounds:=  top: 0, left: 0, bottom: 1600, right: 2560

Display: 1

Display Bounds:=  top: 0, left: -2560, bottom: 1600, right: 0

Video Card Number: 1

Video Card: ATI FirePro V8800 (FireGL)

OpenCL Unavailable

Driver Version: 8.911.3.3000

Driver Date: 20120309000000.000000-000

Video Card Driver:

 

aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiu md64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva ,atiumd6a.cap,atitmm64.dll

Video Mode: 2560 x 1600 x 4294967296 colors

Video Card Caption: ATI FirePro V8800 (FireGL)

Video Card Memory: 2048 MB

Video Rect Texture Size: 16384

Serial number: 90148609589462100194

Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\

Temporary file path: C:\Users\Ivy1\AppData\Local\Temp\

Photoshop scratch has async I/O enabled

Scratch volume(s):

  E:\, 238.5G, 154.4G free

Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\

Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\

Additional Plug-ins folder: not set

 

(shortened)

Optional and third party plug-ins: NONE

 

Plug-ins that failed to load: NONE

Flash:

   Mini Bridge

   Kuler

Installed TWAIN devices: NONE

I am struggling to optimize my computer for Photoshop.

This example file opens in 85 seconds. Same file saves in 340 seconds.

 

 

PhotoShop CS6 (13.0.1)

File is 21000 x 21000 - 50 layers (5.8gb .psb saved)

Why so big? - 5k.com/C.jpg

When open image, I see 2 swap files 67gb & 8.5gb

 

Hard drives

c: Samsung 830 256 ssd boot drive.

Raid0 SSD Samsung 840Pro 256x2 (512total) PSswap/temp (Tests @1100mb/s read @880mb/sec write)(Z77 intel RST v11.0+ raid0 trim)

Samsung 830 ssd media drive (open & save)

File opens in 90 seconds. Saves in 340 seconds.

stays at 0% saved for 270 secs

 

INTEL I7 3770K 3.5G 8M R8 - CPUs utilization - about 12%+- overall - no one cpu above 50%

ASUS SABERTOOTH Z77 lga 1155 MoBo

MEM 8Gx4|GSKILL F3-1866C10Q-32GXL R

 

variables:

tried video card at (Adv, int, basic) no change.

Toyed with an NVIDIA QUADRO 6000 PCI-E 6GB - did not see performance change.

Tried opening&saving to raid0 SSD no change.

switched PSswap & media drives - slowed it down on open & close +- 100sec.

 

I don't understand why it would take so much longer to save than open....

Would a better video card (4gb or 6gb) make a difference?

Would 64gb ram (dif mobo) or 6 core i7-39*0K CPU make a difference?

 

When I pan to bottom-right of image there is a major lag in display. Up to 20 sec. regardless of video settings.

Is there an easy way to calculate video ram needs based on image size? Prefer ATI - was looking at trying v9800 4gb.

 

I recall reading that with SSD drives, having seperate drives for OS, TMP, Media is no longer adventageous....True/False?

 

I am grasping at straws to figure out what my bottlenecks are and how to elliminate them.

 

SysInfo

Adobe Photoshop Version: 13.0.1 (13.0.1 20120808.r.519 2012/08/08:21:00:00) x64

Operating System: Windows 7 64-bit

Version: 6.1 Service Pack 1

System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading

Physical processor count: 4

Logical processor count: 8

Processor speed: 3510 MHz

Built-in memory: 32723 MB

Free memory: 5709 MB

Memory available to Photoshop: 29745 MB

Memory used by Photoshop: 84 %

Image tile size: 128K

Image cache levels: 4

OpenGL Drawing: Enabled.

OpenGL Drawing Mode: Basic

OpenGL Allow Normal Mode: True.

OpenGL Allow Advanced Mode: True.

OpenGL Allow Old GPUs: Not Detected.

Video Card Vendor: ATI Technologies Inc.

Video Card Renderer: ATI FirePro V8800 (FireGL)

Display: 2

Display Bounds:=  top: 0, left: 0, bottom: 1600, right: 2560

Display: 1

Display Bounds:=  top: 0, left: -2560, bottom: 1600, right: 0

Video Card Number: 1

Video Card: ATI FirePro V8800 (FireGL)

OpenCL Unavailable

Driver Version: 8.911.3.3000

Driver Date: 20120309000000.000000-000

Video Card Driver:

 

aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiu md64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva ,atiumd6a.cap,atitmm64.dll

Video Mode: 2560 x 1600 x 4294967296 colors

Video Card Caption: ATI FirePro V8800 (FireGL)

Video Card Memory: 2048 MB

Video Rect Texture Size: 16384

Serial number: 90148609589462100194

Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\

Temporary file path: C:\Users\Ivy1\AppData\Local\Temp\

Photoshop scratch has async I/O enabled

Scratch volume(s):

  E:\, 238.5G, 154.4G free

Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\

Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\

Additional Plug-ins folder: not set

 

(shortened)

Optional and third party plug-ins: NONE

 

Plug-ins that failed to load: NONE

Flash:

   Mini Bridge

   Kuler

Installed TWAIN devices: NONE

 

Message was edited by: PECourtejoie

 
Replies
  • Currently Being Moderated
    Jan 26, 2013 5:13 PM   in reply to edho3456321

    For a 5.8 Gig file, it might take that long.

     

    It takes a lot longer to compress data than to decompress.

     

    But you can try disabling ZIP/Flate compression when saving PSD/PSB in Photoshop's preferences.

    That will make the file huge, but it will save a lot faster.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 26, 2013 5:44 PM   in reply to edho3456321

    This might be a good use for the "save in background" option.

     
    |
    Mark as:
  • Noel Carboni
    23,455 posts
    Dec 23, 2006
    Currently Being Moderated
    Jan 26, 2013 6:34 PM   in reply to edho3456321

    That sounds like a pretty big document considering all the layers.  What's the nature of all those layers?  Pixel data edge to edge, or some vector data, some adjustment layers, a mix?  Do the layers have masks?

     

    I was curious, so I timed the saving of a very large image I have on hand, with 32009 x 21000 pixels, 16 bits/channel, 42 layers, some pixels, some adjustment layers, most layers with masks.  I have "Maximize Compatibility" set to "Never" and I enabled Flate compression.  The save was to a high bandwidth SSD array, and like you I have Windows 7 x64.

     

    The save went like this:

     

    It started at 0%

    Jumped to 25% at 8 seconds into the save.

    26% at 0:35

    27% at 1:30

    28% at 3:15

    etc. at long intervals.  The file psA3B2.tmp grew incrementally all during that time.

    It seemed to stop at 73% for a few minutes.

     

    The save completed in 22 minutes 10 seconds and the .psb file was ultimately 6.6 GB in size.

     

    Since I have Background saving enabled in Photoshop CS6 I was able to interact with Photoshop and could potentially have been continuing editing during that time.  Also I had no problem doing other things, like type up this message, chat on Skype, etc.

     

    I have 48GB of RAM and actual usage rose to 43.4 GB.  Photoshop created a 58GB scratch file.

     

    It busied one logical processor (of 24) pretty much to the max the entire time (showing a total of 4% usage).  As I understand it data compression is not something easily multi-threaded (though I wonder whether it could be done by multiple threads on a layer by layer basis).  Your core speed is faster than mine with that i7-3770K processor (as compared to my Xeon X5690 CPUs), and who knows how different our documents are, but I'd say your system did rather well given that you have compression enabled.

     

    The real workaround that could make it more usable for you is what Chris said above - for a document at this magnitude in size, disable the Flate compression and it will get right to the task of saving to disk.  And yes, it will make the file HUGE - so you trade size for speed.

     

    As a test I disabled compression and saved again.  This time the save completed in 1 minute 29 seconds and the .psb file ended up being 36.5 GB in size.

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    23,455 posts
    Dec 23, 2006
    Currently Being Moderated
    Jan 26, 2013 6:45 PM   in reply to edho3456321

    As to why your system would sit for so long before showing progress...  Did you try running the Resource Monitor?  I'll bet you're swapping a lot to the HDD.  I see you have your scratch area pointed to your HDD...  That's going to slow things down TREMENDOUSLY.

     

    You might just have a shortage of RAM coupled with big slowdowns owing to your scratch drive being pretty slow (by comparison to SSD storage).

     

    I have my scratch pointed to my SSD array.

     

    How much free space do you have on your SSD?  If more than enough, you *could* make it the first scratch drive, then make the one you're using now the second one.

     

    If not, maybe you could get another one strictly for scratch use.  Or maybe this is your excuse to upgrade your RAM (4x as much ought to be better) and get a whole bunch more SSDs and build an array of them. 

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    23,455 posts
    Dec 23, 2006
    Currently Being Moderated
    Jan 26, 2013 6:53 PM   in reply to Noel Carboni

    EDIT: Scratch that - I re-read your specs and misinterpreted what you'd written. I see you already have an SSD array.

     

    Seems to me putting all the SSDs in one array might be better.  It gives peak bandwidth when needed (busying all the SATA links at once) and consolidates all your free space.   It seems to work for me (I have 4 x 480 GB OCZ Vertex 3 SSDs, 1.7 GB/sec).

     

    But I think your main problem with working with documents that size is that you have a lack of RAM.  That probably is why my system got right to the task of saving instead of waiting that initial several minutes.

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    23,455 posts
    Dec 23, 2006
    Currently Being Moderated
    Jan 27, 2013 11:11 AM   in reply to edho3456321

    I find it a little hard to believe the file size is the same with and without compression...  Exactly what setting are you changing?  This one?

     

    DisableCompression.png

     

    Are you willing to share the full-sized file online?  If so you can PM me if you'd like.  I have a fiber internet link so downloading a few gigabytes is no big deal.

     

    I can try with specifically your file to see if I experience the same difference in speed as with my file.

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    23,455 posts
    Dec 23, 2006
    Currently Being Moderated
    Jan 27, 2013 4:08 PM   in reply to edho3456321

    I guess you must truly have incompressible data then. 

     

    Glad to hear you found the Image Preview setting a way to speed things up.  It's been a long time since I made that change, and I didn't even think of it.

     

    -Noel

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points