tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pid <>
Subject Re: Java process killed by oom-killer in Ubuntu
Date Thu, 14 Jun 2012 09:01:36 GMT
On 12/06/2012 14:50, Christopher Schultz wrote:
> Pid,
> On 6/12/12 5:47 AM, Pid wrote:
>> On 11/06/2012 20:15, Christopher Schultz wrote:
>>> Also, your previously-posted configuration seems a little
>>> insane:
>>>> Xms6g -Xmx6g -XX:NewSize=4G -XX:MaxNewSize=4G
>>>> -XX:SurvivorRatio=6 -XX:MaxPermSize=512M
>>>> -XX:-UseConcMarkSweepGC -XX:+UseStringCache 
>>>> -XX:+HeapDumpOnOutOfMemoryError 
>>>> -XX:HeapDumpPath=/home/example/logs
>>> -Xmx6g and NewSize=4G? Plus 0.5G for PermGen?
>> I think you'll run into trouble setting the NewSize that large. 
>> There's a reason that the NewRatio works the way it does.
>> Sun advice always used to be "keep the eden size between 1/4th and
>> 1/3rd the maximum heap size".  You are specifying 2/3rd the max
>> heap.
> +1
> I don't know what happens during a collection if the survisor space is
> too small for all the objects being promoted from eden... does the MM
> just randomly promote objects to the old space?

I don't know either for certain, but I'd not be surprised if Bad Things

I think you'd probably see a bunch of full collections in the run up to
that situation & your performance would fall off a cliff.  You might get
an OOM before it got there, depending on the GC algo in play.




View raw message