lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis.gospodne...@gmail.com>
Subject Re: Garbage Collection tuning - G1 is now a good option
Date Wed, 07 Jan 2015 16:06:45 GMT
Not sure about AggressiveOpts, but G1 has been working for us nicely.
We've successfully used it with HBase, Hadoop, Elasticsearch, and other
custom Java apps (all still Java 7, but Java 8 should be even better).  Not
sure if we are using in on our Solr instances.

e.g. see http://blog.sematext.com/2013/06/24/g1-cms-java-garbage-collector/

Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/


On Thu, Jan 1, 2015 at 8:35 PM, William Bell <billnbell@gmail.com> wrote:

> But tons of people on this mailing list do not recommend AggressiveOpts
>
> Why do you recommend it?
>
> On Thu, Jan 1, 2015 at 12:10 PM, Shawn Heisey <apache@elyograg.org> wrote:
>
> > I've been working with Oracle employees to find better GC tuning
> > options.  The results are good enough to share with the community:
> >
> > https://wiki.apache.org/solr/ShawnHeisey#GC_Tuning
> >
> > With the latest Java 7 or Java 8 version, and a couple of tuning
> > options, G1GC has grown up enough to be a viable choice.  Two of the
> > settings on that list were critical for making the performance
> > acceptable with my testing: ParallelRefProcEnabled and G1HeapRegionSize.
> >
> > I've included some notes on the wiki about how you can size the G1 heap
> > regions appropriately for your own index.
> >
> > Thanks,
> > Shawn
> >
> >
>
>
> --
> Bill Bell
> billnbell@gmail.com
> cell 720-256-8076
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message