[Daniel Bayer]

I just got my powerbook 17 up to the 2GB mark with ram.

My main application is Photoshop CS. I have 70% of the avaliable ram (1.85 GB with OSX considered ) allocated to it, about 1.3GB.

Is that going to create problems for the other apps that might be open? I usually will have iVew Media pro and mail open. I also might have itunes and safari open, but that is usually it while cranking hard in PS.

Input??

[tooki]

For optimum performance, Photoshop needs about 30-50MB for itself, plus 5 times the uncompressed file size of the images.

So, for example, if you usually have two 20MB images open, then PS needs (2x20x5)+50=250MB.

Remember that each layer is a whole separate image.

As long as the OS isn't swapping out, you should be OK. If you do start to swap to disk, reduce Photoshop's memory allocation: Photoshop's dedicated, tailored disk swapping is MUCH more efficient than the all-purpose system swapping.

tooki

[Daniel Bayer]

Originally posted by tooki:
For optimum performance, Photoshop needs about 30-50MB for itself, plus 5 times the uncompressed file size of the images.

So, for example, if you usually have two 20MB images open, then PS needs (2x20x5)+50=250MB.


Remember that each layer is a whole separate image.

As long as the OS isn't swapping out, you should be OK. If you do start to swap to disk, reduce Photoshop's memory allocation: Photoshop's dedicated, tailored disk swapping is MUCH more efficient than the all-purpose system swapping.


tooki

Wow, that is alot for a couple of smallish files. My files average 60-80MB, some as high as 200MB not interpolated. I opened a 204MB tiff file and rotated it four times completly around to see how it would do with the big ram, it took 3 seconds on the average to rotate and re-draw, the scratch size after 4 rotations was over 2.2 GB!

Thanks Tooki!

[larkost]

I would take that 5x estimate and trim it to 3x or so. Other than that... I agree with tooki that it really does want that much memory. Having multiple VM systems on top of each other is a very bad idea.

Oh... and the real hog on memory is not layers (although they are a compounding issue) but is the history system. If you reduce the number of history states active you will reduce the footprint.