My first question would be, do you need 16GB of heap, thats a lot and
will contribute to long pauses, what happens if you try it out with 8GB,
are you trying to be too greedy with the caches ?
You question is very open ended, tuning a GC is an art from, what works
for one workload is often quite wrong for another, are you using any JVM
flags what are they ?
If you put the following on your JVM arguments, and then put the log
somewhere on the internet it will make it easietr to fgure out what
might be wrong
-Xloggc:gc.log -XX:+NUMAStats -XX:+PrintCMSInitiationStatistics
-XX:+PrintFlagsFinal -XX:+PrintGCApplicationConcurrentTime
-XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDetails
-XX:+PrintGCTimeStamps -XX:+PrintJNIGCStalls -XX:+PrintReferenceGC
-XX:+PrintTenuringDistribution
-- Greg
On 29/06/2012 20:09, Bill Bell wrote:
We are getting large Solr pauses on Java garbage collection in 1.6 Java.
We have tried CMS. But we still have. 4 second wait on GC.
What works well for Solr when using 16 GB of RAM?
I have read lots of articles and now just looking for practical advise and
examples.
Sent from my Mobile device
720-256-8076
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
