Views
259
Replies
5
Status
Closed
I’ve searched and read up about this, but still haven’t found an answer. I have a 10 gig dedicated scratch disk. Recently, I added RAM to get my system up to 3 gigs. After reading, I set the 3 gig switch, and it worked so I could allocate more ram to PS. I’m using cs3, and have the ram set to 65% (about 1.7 gigs). Other than OS stuff, I have no other apps running.
Here’s the situation. I’m working with 16 bit images of around 50 megs. If I open one image, do my edits, save, and quit the image. I must wait about 7-10 seconds while the scratch disk is being erased. I have checked my efficiency and it never drops below 100%. When I first open an image, I can watch PS start to write to the HD. If I do about 5 edits and close, I wait. Even if all my edits use up 20x the image size, I’m only using 1 gig of memory, and ps still has 700 megs left over. BTW, I’ve tried setting memory allocation to 55%, and it still happens.
The question is why, with so much available RAM, is PS using the scratch disk?
Thanks.
Here’s the situation. I’m working with 16 bit images of around 50 megs. If I open one image, do my edits, save, and quit the image. I must wait about 7-10 seconds while the scratch disk is being erased. I have checked my efficiency and it never drops below 100%. When I first open an image, I can watch PS start to write to the HD. If I do about 5 edits and close, I wait. Even if all my edits use up 20x the image size, I’m only using 1 gig of memory, and ps still has 700 megs left over. BTW, I’ve tried setting memory allocation to 55%, and it still happens.
The question is why, with so much available RAM, is PS using the scratch disk?
Thanks.
How to Master Sharpening in Photoshop
Give your photos a professional finish with sharpening in Photoshop. Learn to enhance details, create contrast, and prepare your images for print, web, and social media.
