Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: [Digital BW] computer horsepower ?

2005-02-27 by Steve Kale

The 2 gb limit is fact.  But there is a lot of pushing on the Adobe Feature
Request sub forum for an extension of the limit for 64 bit processor
machines.

But guys - this is now way off-topic.


> From: Seth <seth@...>
> Organization: Serh Rossman Photography
> Reply-To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
> Date: Sun, 27 Feb 2005 08:41:24 -0500
> To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
> Subject: RE: [Digital BW] computer horsepower ?
> 
> 
> I, too, have seen the 2GB limit.  I think it was from Chris Cox on the PS
> list.
> 
> But, I think you're right about everone's magic number.  A LOT depends on
> tweaking of services and the registry which is not for the faint of heart.
> 
> One thing people can do is check how the "startup priority" is set.  If it
> is not set to the foreground program having priority it can dog a low RAM
> system down.
> 
> Regardless of which machine I use I set PS to 70-79%.  Again (ad nauseum)
> having a swap drive for PS separate from the startup can be a large factor,
> depending on the machine.
> 
> Seth
> 
> ==-----Original Message-----
> ==From: Bob Frost [mailto:bob@...]
> ==
> ==From my experience, you have to find the magic number for
> ==yourself. It depends on what RAM you have, what plugins you
> ==want to run (some use part of PS's memory allocation, and
> ==some want memory outside), and what other programs you might
> ==want to run at the same time as PS. With 4GB RAM, I find I
> ==can now allocate 90% to CS and still use the NeatImage
> ==plugin, whereas previously (with only 2GB RAM) I had to
> ==reduce it to below 60%. And I can allow Capture to sit in the
> ==background, whereas previously I had to shut it down to get
> ==CS working reasonably fast.
> 
> 
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.