Generally speaking its the same as the Java Runtime limits. That
would be about 1.5GB on all older versions of Mac OS X (Tiger and
older).
However, if you're running Leopard on an 64-bit Intel processor then
the limit is much higher. A lot higher. It could, in theory, go as
high as you have HD space for the virtual memory. You just have to
use the -d64 command line flag along with the -Xmx setting. Also,
you'll have to tweek the application's startup script to get around
the path bug that causes the JVM to think it can't do 64-bit mode
when, in fact, it can.
But that's only for 64-bit Intel processors running Leopard. If
you're running any PowerPC processors (including the G5) then you're
stuck with the 32-bit JVM.
--
Galen Rhodes
[EMAIL PROTECTED]
On Jan 11, 2008, at 1:34 PM, Jeff Schmitz wrote:
Hello,
What is the max memory allocation you can assign to on application
instance (assuming of course you have the memory installed) on a
previous generation Xserve with Tiger Server/WO5.3? How about the
latest xserve with Leopard Server/WO5.4?
Thanks,
Jeff
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/grhodes%40thissmallworld.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
