cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10403) Consider reverting to CMS GC on 3.0
Date Wed, 14 Oct 2015 16:00:09 GMT

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

Joshua McKenzie commented on CASSANDRA-10403:
---------------------------------------------

So after working through a force-push nuking the .ps1 change on your branch (addressed offline),
my last question:

{noformat}
...
conf/logback.xml etc/cassandra
conf/logback-tools.xml etc/cassandra
conf/jvm.options etc/jvm.options
...
{noformat}
Are we intending to drop jvm.options into /etc rather than /etc/cassandra? That seems off
to me. I haven't tested the cassandra.install changes - I assume you tested this and it's
working?


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

Mime
View raw message