Unfortunately, G1 on Java 6 was a bust. Several times GC pauses made my
load balancer think the server was down, just like with CMS/ParNew.
Either there's something about my production query patterns that doesn't
get along with any of the garbage collection methods, or I need to
upgrade to Java 7.
I have tried lowering my max heap before. That results in OOM problems
when I do full-import with DIH.
On 1/20/2013 2:13 PM, Markus Jelsma wrote:
Hi Shawn,
Although our heap spaces are much less than yours (256M for 2x 2.5GB cores per
node) we saw decreased throughput and higher latency with G1 on Java 6. You can
also expect higher CPU consumption. You can check it very well with VisualVM
attached.
Looking forward to your results.
Markus
-----Original message-----
From:Shawn Heisey <s...@elyograg.org>
Sent: Sun 20-Jan-2013 21:48
To: solr-user@lucene.apache.org
Subject: Re: Long ParNew GC pauses - even when young generation is small
On 1/18/2013 10:07 PM, Shawn Heisey wrote:
I may try the G1 collector with Java 6 in production, since I am on the
newest Oracle version.
I am giving this a try on my secondary server set. An encouraging note:
The -XX:+UnlockExperimentalVMOptions option is no longer required to use
the G1 collector, at least on version 6u38.
Thanks,
Shawn
