indeed, helpful
thanks!
On Fri, Jun 3, 2016 at 9:31 PM, Spico Florin wrote:
> than you very much for sharing these. i hope that others will contribute.
> regards,
> florin
>
>
> On Friday, June 3, 2016, Stephen Powis wrote:
>
>> Here's the flags
than you very much for sharing these. i hope that others will contribute.
regards,
florin
On Friday, June 3, 2016, Stephen Powis wrote:
> Here's the flags we're using:
>
> -Xms3G -Xmx3G -XX:MaxPermSize=100M -Xloggc:gc-%ID%.log
> -XX:+PrintGCDateStamps -XX:+PrintGCDetails
Here's the flags we're using:
-Xms3G -Xmx3G -XX:MaxPermSize=100M -Xloggc:gc-%ID%.log
-XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintTenuringDistribution
-XX:+PrintGCApplicationStoppedTime -XX:+DisableExplicitGC
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=50M
Hi,
+1 for G1 for large heaps where you are seeing big GC pauses. Works well
for us.
See:
https://sematext.com/blog/2013/06/24/g1-cms-java-garbage-collector/
Otis
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training -
Hello!
I would like the community the following:
1. Are you using the G1 garbage collector for your workers/supervisors in
production?
2. Have you observed any improvement added by adding this GC style?
3. What are the JVM options that you are using and are a good fit for you?
Thank you in
Hello!
I would like the community the following:
1. Are you using the G1 garbage collector for your workers/supervisors in
production?
2. Have you observed any improvement added by adding this GC style?
3. What are the JVM options that you are using and are a good fit for you?
Thank you in