9 Replies Latest reply: Jan 1, 2012 1:50 PM by Imworkinghere RSS

    VERY slow performance with CS4 + Save for web

    ibattersby Community Member

      Note: I have done a search for similar issues but can find nothing regarding CS4 and this particular issue. I'm using a MacBook Pro 2.4Ghz w/4GB of RAM and resources are aplenty when the issue occurs.

       

      Issue

      My problem is that under certain circumstances the 'save as web' function can take upto 3 minutes before the diaglog box appears. I've had this for some time but only in the last couple of days did I notice something that might be relevant:

       

      Works

      1. Open 3 large TIFF files @ 120mb approx (mine are 3 processed RAW files from Capture One / 4200x5600@300dpi)

      2. Create a new adjustment layer for each image

      3. Resize each image to 72dpi @ 800x600

      4. Run a SmartSharpen & flatten layers

      5. In each tab (for each image) do 'save as web'

      6. 'Save as web' dialog appears in expected time

       

      VERY slow

      1. Open 3 large TIFF files @ 120mb approx (mine are 3 processed RAW files from Capture One / 4200x5600@300dpi)

      2. Create a new adjustment layer for each image

      3. Resize each image to 72dpi @ 800x600

      4. Run a SmartSharpen & flatten layers for each image

      5. In first tab do 'save as web'

      6. 'Save as web' dialog appears in expected time

      7. Close this document (tab)

      8. Go to the next image (tab) and do 'save as web'

      9. Dialog box can take anything from 20secs to 3mins to appear.

      10. Close this document (tab)

      11. Go to the last image (tab) and do 'save as web'

      12. Dialog box can take anything from 20secs to 3mins to appear.

       

      As I can easily go through this process for 50-60 images you can imagine that it can waste over an hour of my time waiting for Photoshop to get it's act together. I assume it's something todo with memory allocation, or that it's processing previews for all three tabs on the first 'save as web', but in any respect it's very annoying. There seems nothing obviously wrong resource-wise at the time of doing these.

       

      Would be interested if anyone else has this issue!

       

      Thanks!