G1 "to-space exhausted" causes used heap space to increase?

[Christopher Berner]

We're just running with the default IHOP

On Mon, Mar 2, 2015 at 10:15 AM, Simone Bordet <simone.bordet at gmail.com>
wrote:

> Hi,
>
> On Mon, Mar 2, 2015 at 6:44 PM, Christopher Berner
> <christopherberner at gmail.com> wrote:
> > Hello,
> >
> > I work on the Presto project (https://github.com/facebook/presto) and am
> > trying to understand the behavior of G1. We run a 45GB heap on the worker
> > machines with "-XX:G1HeapRegionSize=32M", and it works smoothly,
>
> Just out of curiosity, you seem to have IHOP=45% and an eden that is
> 55% of the heap (25 GiB out of 45 GiB).
> Is there any reason why you keep IHOP this low or you're just running
> with defaults ?
>
> To the hotspot gc experts, is there any way to limit the Eden size
> without impacting on the ergonomics ?
> Does -XX:MaxNewSize impact ergonomics ?
>
> --
> Simone Bordet
> http://bordet.blogspot.com
> ---
> Finally, no matter how good the architecture and design are,
> to deliver bug-free software with optimal performance and reliability,
> the implementation technique must be flawless.   Victoria Livschitz
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-gc-use/attachments/20150302/639c9ac7/attachment.html>