G1 GC for 100GB+ heaps

[Kees Jan Koster]

Dear Tao,

Thank you for the response. We will enable GC logging and see what we can learn from it.

> I had experience in tuning G1 with ~30GB in production environment (not as large as you attempt :). I found it helpful to play around the following JVM options as well as Java monitoring tools such as Jconsole/JMC:
> 
> -Xmx<nG> -Xms<nG>
> -XX:MaxGCPauseMillis=<ms>
> -XX:InitiatingHeapOccupancyPercent=<%>
> -XX:+PrintReferenceGC
> -XX:+ParallelRefProcEnabled
> -XX:+PrintAdaptiveSizePolicy
> -XX:ParallelGCThreads=n
> -XX:ConcGCThreads=n
> -XX:G1MixedGCCountTarget=n
> 
> As for region sizing, since you have a large heap, you may want to check the relationship of region sizes and humongous object allocation, making sure they are harmonious. If you suspect any problem in that end, you can try G1PrintHeapRegions to diagnose.


--
Kees Jan

http://java-monitor.com/
kjkoster at kjkoster.org
+31651838192

I hate unit tests; I much prefer the illusion that there are no errors in my code.
                                                                 -- Hendrik Muller

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.openjdk.java.net/pipermail/hotspot-gc-use/attachments/20150723/34c4452b/signature.asc>