If you believe the logs, using -XX:+PrintGCApplicationStoppedTime is probably the easiest way to avoid having to try to parse pause times from various formats. But remember, GC logs can [often unintentionally] lie (I've seen them under-report by multi-second gaps).
If you want to actually measure your JVM pauses (GC or others), you can use something like jHiccup (http://www.azulsystems.com/jHiccup). It is a free (as in beer) and public domain (CC0) tool that will show you any blip/glitch/hiccup that you jvm experiences while running your application, and report it in both time based and detailed percentile form. What jHccup shows you is a "best-case" response time for your applicartion as it runs (the response time the application would have shown if completed everything as zero work). It's near-trivial to add jHiccup to your environment (as either a java agent or wrapper script). It would be interesting to see the percentile histograms (jHiccup's .hgrm text output) for your environment. -- View this message in context: http://lucene.472066.n3.nabble.com/Long-ParNew-GC-pauses-even-when-young-generation-is-small-tp4031110p4034934.html Sent from the Solr - User mailing list archive at Nabble.com.
