JEP 141: Increase the Client VM's Default Heap Size

Vitaly Davidovich vitalyd at gmail.com
Wed Feb 22 07:55:22 PST 2012


I think the impression could also be based on virt mem size of the process
(I.e. committed + reserved).  The failure to start is probably a real
concern for OS's without overcommit, especially if multiple java procs are
running at the same time.

Sent from my phone
On Feb 22, 2012 10:40 AM, "Jon Masamitsu" <jon.masamitsu at oracle.com> wrote:

>
>
> On 2/22/2012 4:28 AM, Michael Bien wrote:
>
>>  On 02/22/2012 12:48 AM, mark.reinhold at oracle.com wrote:
>>
>>> Posted: http://openjdk.java.net/jeps/**141<http://openjdk.java.net/jeps/141>
>>>
>>> - Mark
>>>
>>>  additional risks:
>>  - JVM may not be able to start
>>
>
> Specifically, the JVM tries to reserve enough memory at start up
> for the heap and fails to initialize if it cannot?
>
> Will add it.
>
>   - could contribute to the false impression that java requires a lot of
>> memory to run (JVMs usually don't like to give memory back to the OS once
>> its in use)
>>
>
> Is this an impression the user would get because the JVM would not start
> up as you
> note above?   The JVM does not necessarily use all the memory it reserves.
>
>
> Thanks.
>
> Jon
>
>>
>> best regards,
>> michael
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20120222/a9752e57/attachment.html 


More information about the hotspot-gc-dev mailing list