G1gc compaction algorithm
Yu Zhang
yu.zhang at oracle.com
Thu Jul 31 06:46:03 UTC 2014
Martin,
Thanks for the logs.
With 4m regions size, after marking, there are 252 HUMS and 80 HUMC regions.
With 4m regions size, after marking, there are 1HUMS and 0 HUMC regions.
The larger region size reduced Humongous allocation greatly. The mixed
gc can not clean much due to predicted time too high. I think we need
to reduce other pause time first: UpdateRS, ScanRS, Other...
I will get back to you after taking a closer look.
Thanks,
Jenny
On 7/28/2014 8:27 PM, Martin Makundi wrote:
> Hi!
>
> We suffered a couple of Full GC's using regionsize 5M (it seems to be
> exact looking at logged actual parameters) and we tried the 16M option
> and this resulted in more severe Full GC behavior.
>
> Here is the promised log for 16 M setting:
> http://81.22.250.165/log/gc-16m.log
>
> We switch back to 5M hoping it will behave more nicely.
>
> **
> Martin
More information about the hotspot-gc-use
mailing list