Re: Memory control
Re: Memory control
- Subject: Re: Memory control
- From: Pascal Robert <email@hidden>
- Date: Fri, 18 Mar 2011 08:33:03 -0400
Le 2011-03-18 à 08:24, Gennady Kushnir a écrit :
>>>> 64M seems small to me for a Java app.
>>> I did not do any memory regulations myself. It is just default on my
>>> absolutely standard deployment system for WO (Xserve G4 , 2GB, MacOS X
>>> 10.5, Java 1.5.0_24)
>>>
>>> I found this 64M doing
>>> ps ax | grep "java"
>>>
>>> It lists all WO apps like this:
>>> /usr/bin/java -XX:NewSize=2m -Xmx64m -Xms32m -DWORootDirectory=/System ...
>>
>> If you look at the entire line, you will often see these set multiple times with different values. The last one is what is used.
>
> I could not find any other values set in that line...
> So Chuk, you also propose to raise this default?
>
> This causes me to ask another question. What is better scalability
> mechanism? Increasing memory for single instance or adding extra
> instances?
> Raising memory seems more resource effective. So why would I use
> multiple instances on single server? Or such means are some kind of
> rudiment?
It depends in part if the app have to be up 99.9% of time. If the app is critical, it's always good to have more than one instance so that if one instance deadlock (or get out of memory errors), at least you have another instance running.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden