Please bear in mind many user's requirements are different, so...these are my current opinions on the matter at hand. ;0)Date: Fri, 17 Jan 2003 16:34:17 +0000 From: ashley karyl <[EMAIL PROTECTED]>But how much RAM do you have and how big are your files on average? Ashley
(1.5gRAM/933 dual G4 averaging 300mb-to-1.97gig files.)
Here's my crib notes on fine tuning my OS and PShop allocations:
(I'll refer to the colored system dial as Sysdial and PS clock as PSclock.)
When allocating your resource percentage: the Memory and Caching Menu (PS Preferences) shows you how much active RAM will be allocated to PS in relation to percentage of System Resources. Note that PS (and other apps) will use as much as 97.7 of CPU to perform immediate on-demand commands, however, actual memory usage and performance overall will also be affected by how much virtual memory caching is going on in the background; in particular how efficient the OS is in utilizing application background caches with actual system virtual memory caches appears to be the real question at present. The OS virtual memory caching causes performance decrease in applications which cache to the same harddisk.
Two improvments of note:
1. Using a secondary hard disk as Primary caching in PS improves performance.
2. Disabling Photoshop's Plug-Ins>AdobePhotoshopOnly>Extensions>EnableAsyncI/O (by putting a tilde ~ in front of the folder name) provides on-demand caching and processing. The current default On should now be default Off under OSX.
My BeigeG3 test computer has only 328MB and I do not get a Sysdial with allocation at 61 percent (280 MB test file). Instead I get the PSclock when performing PSactions which address virtual memory and caching.
On my G4 editing station, alternating between 48-91 percent in attempts to force use of the actual memory in place only makes a difference when toggling between multiple OS and other applications (other than PS) while PS performs actions in the background.
If only working in PS push your resources high to improve application performance.
If other system operations (OS responsiveness) are important: bring PS allocation down till OS responsiveness suits your needs while PS is running.
PS7 handles memory allocations on the fly. The TrueBlueEnvironment of OSX.2 seems to be able to handle the toggling well so...
Opening ProcessViewer set to User Processes and performing large actions (open 20-30 files and start copying and pasting, transforming, distorting, run a few Miranda plug-ins, batch process etc.) CPU usage rockets, but actual PS memory usage seldom rises above 64 percent even with PS allocation at 91 percent. (Note: seldom)
In a dormant state PS seems to settle at 43 percent resources with all plug-ins and other PS resources in place.
Stripping down PS's extra plug-ins and unused filters appears to bring that allocation down though not significantly.
Overall I'm not sure if this is an OSX.2 thing or a PS7 thing or my particular workstation thing, but I do know that pulling a 512MB RAM card out still gives the same performance results which leads me to think how the OS addresses dual and other processors may be part of the answer.
In short, more RAM allows OSX application and system allocations to read/write caching more effectively. Any computer or cpu can only process as fast as its limitations. Disabling Enable AsyncI/O in PS and then fine tuning PS's allocation to suit your OS or your Application needs appears to be more important in terms of efficiency and getting the most out of your OS/PS operations than simply adding massive amounts of RAM. (Though lots of RAM helps.)Richard Lewisohn writes: Does that imply that you can have too much RAM? I thought more was better. I've got 1GB of RAM on a 933mhz G4 and have allocated more than 61%. Is less really more? Regards
Using step 1 and 2 above: both my G4 and G3 improved memory and caching performance under OSX.2.
Last benchmark test:
Simultaneously: opened 8 200 mb files (tiffs) in PS7
opened two 300 mb files ins PS6(Classic)
boot iTunes and listen to Cowboy Cultural Society at 2:00 marker (no performance decrease)
Fiddle with InDesign files while waiting
Total opening time to instant preview: 5:12
Note: no spinning system dials.
Sorry for the ramble. trying to work and write and test at the same time...;0)
;0)
--
joel johnstone
Color Canuck
(A lesser-known of the Great Northern Joels)
===============================================================
GO TO http://www.prodig.org for ~ GUIDELINES ~ un/SUBSCRIBING ~ ITEMS for SALE
