[jira] Commented: (ZOOKEEPER-545) investigate use of realtime gc as the recommened default for server vm
[ https://issues.apache.org/jira/browse/ZOOKEEPER-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12800968#action_12800968 ] Patrick Hunt commented on ZOOKEEPER-545: I've had alot of luck recently using the latest 1.6.0 jvm (_17) along with CMS/incremental. Question is, what should we do, just update the docs or make changes in the source as well. For example we could change the tests to run with CMS/Incremental. investigate use of realtime gc as the recommened default for server vm -- Key: ZOOKEEPER-545 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-545 Project: Zookeeper Issue Type: Improvement Components: server Reporter: Patrick Hunt Priority: Critical Fix For: 3.3.0 We currently don't recommend that ppl use the realtime gc when running the server, we probably should. Before we do so we need to verify that it works. We should make it the default for all our tests. concurrent vs g2 or whatever it's called (new in 1.6_15 or something?) Update all scripts to specify this option update documentation to include this option and add section in the dev/ops docs detailing it's benefits (in particular latency effects of gc) Also, -server option? any benefit for us to recommend this as well? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-545) investigate use of realtime gc as the recommened default for server vm
[
https://issues.apache.org/jira/browse/ZOOKEEPER-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771096#action_12771096
]
Jean-Daniel Cryans commented on ZOOKEEPER-545:
--
Patrick,
Here's the configuration we currently ship with HBase to solve most of the
basic problems seen by new users:
{noformat}
-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
{noformat}
Also since 1.6u14 and with 1.7 beta, Java ships with the new G1 GC (paper
http://www.research.sun.com/jtech/pubs/04-g1-paper-ismm.pdf) which get rids of
JVM pauses. You can use the following options to enable it:
{noformat}
-XX:+UnlockExperimentalVMOptions -XX:+UseG1GC
{noformat}
investigate use of realtime gc as the recommened default for server vm
--
Key: ZOOKEEPER-545
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-545
Project: Zookeeper
Issue Type: Improvement
Components: server
Reporter: Patrick Hunt
Priority: Critical
Fix For: 3.3.0
We currently don't recommend that ppl use the realtime gc when running the
server, we probably should.
Before we do so we need to verify that it works.
We should make it the default for all our tests.
concurrent vs g2 or whatever it's called (new in 1.6_15 or something?)
Update all scripts to specify this option
update documentation to include this option and add section in the dev/ops
docs detailing it's benefits (in particular latency effects of gc)
Also, -server option? any benefit for us to recommend this as well?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
