You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/04/23 21:52:18 UTC
[jira] [Updated] (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:all-tabpanel ]
Michi Mutsuzaki updated ZOOKEEPER-545:
--------------------------------------
Fix Version/s: (was: 3.5.0)
3.6.0
> 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
> Labels: newbie
> Fix For: 3.6.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 was sent by Atlassian JIRA
(v6.2#6252)