[jira] [Commented] (ZOOKEEPER-545) investigate use of realtime gc as the recommened default for server vm

["nijel (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053527#comment-14053527 ] 

nijel commented on ZOOKEEPER-545:
---------------------------------

Users will face challenge in setting other GC options also (like mewSize, mx, gcInterval, ms).

Can we have a profile based GC options ?

We can ship a *gc-opts* file with multiple profiles (low,medium and high). Each profile will have set of GC options. The profiles are named in the order of memory configured. Like high can have mx as 4 gb and related configurations. Low can have 512 as mx and related configurations.

So user can just configure the profile name.

As we are getting more improvements, comments can update these values in the file.

> 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)