Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 14 Oct 2015 13:59:05 +0000 (UTC)
From: "Joshua McKenzie (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12901053.1443456530000.37100.1444831145984@Atlassian.JIRA>
In-Reply-To: <JIRA.12901053.1443456530000@Atlassian.JIRA>
References: <JIRA.12901053.1443456530000@Atlassian.JIRA>
 <JIRA.12901053.1443456530912@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-10403) Consider reverting to CMS
 GC on 3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Joshua McKenzie edited comment on CASSANDRA-10403 at 10/14/15 1:58 PM:
-----------------------------------------------------------------------

Sorry for the delay - thought we were waiting on the answer re: package install.

.ps1 changes look good and test correctly. Only one thing left: the GC logging options in jvm.options won't work on Windows if users un-comment those lines as-is. We should probably have a little logic in cassandra-env.* to parse out GC logging options and a simple flag to enable it in the jvm.options file. This shouldn't necessitate a change to the regex/StartsWith checks since the lines start with JVM_OPTIONS, so it should be pretty clean.

Once that's ironed out, I'll commit. (edit: after the debian/cassandra.install changes too)


was (Author: joshuamckenzie):
Sorry for the delay - thought we were waiting on the answer re: package install.

.ps1 changes look good and test correctly. Only one thing left: the GC logging options in jvm.options won't work on Windows if users un-comment those lines as-is. We should probably have a little logic in cassandra-env.* to parse out GC logging options and a simple flag to enable it in the jvm.options file. This shouldn't necessitate a change to the regex/StartsWith checks since the lines start with JVM_OPTIONS, so it should be pretty clean.

Once that's ironed out, I'll commit.


> Consider reverting to CMS GC on 3.0
> -----------------------------------
>
>                 Key: CASSANDRA-10403
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10403
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>            Reporter: Joshua McKenzie
>            Assignee: Paulo Motta
>             Fix For: 3.0.0 rc2
>
>
> Reference discussion on CASSANDRA-7486.
> For smaller heap sizes G1 appears to have some throughput/latency issues when compared to CMS. With our default max heap size at 8G on 3.0, there's a strong argument to be made for having CMS as the default for the 3.0 release.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)