Shawn Heisey kirjoitti 26.9.2018 klo 21.16:
On 9/26/2018 9:35 AM, Jeff Courtade wrote:
My concern with using g1 is solely based on finding this.
Does anyone have any information on this?
https://wiki.apache.org/lucene-java/JavaBugs#Oracle_Java_.2F_Sun_Java_.2F_OpenJDK_Bugs
I have never had a single problem with Solr running with the G1
collector. I'm only aware of one actual bug in Lucene that mentions G1
... and it is specific to the 32-bit version of Java. It is strongly
recommended for other reasons to only use a 64-bit Java.
On the subject of the blog post mentioned by Zisis T... generally
speaking, it is not a good idea to explicitly set the size of the
various generations. G1 will tune the sizes of each generation as it
runs for best results. By setting or limiting the size, that tuning
cannot work with freedom, and you might be unhappy with the results.
Here is a wiki page that contains my own experiments with garbage
collection tuning:
https://wiki.apache.org/solr/ShawnHeisey
There's one caveat that I know of: You might need to modify G1 tuning
parameters if your Solr has dramatically changing usage patterns. For
instance heavy search use during the day and heavy indexing work during
the night. This may lead G1 to optimize too heavily for one and it
taking a while to adjust for the other. At some point I've used e.g. the
following settings to limit the young generation:
-XX:+UnlockExperimentalVMOptions -XX:G1MaxNewSizePercent=5
This was used with a very specific usage pattern, so it probably doesn't
apply in most situations.
Regards,
Ere
--
Ere Maijala
Kansalliskirjasto / The National Library of Finland
