cassandra-commits mailing list archives

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

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

Paulo Motta commented on CASSANDRA-10403:
-----------------------------------------

For some reason, {{cassandra-env.sh}} is called before loading {{debian/cassandra.in.sh}}
on {{debian/init}}. Since the init script already defines {{CASSANDRA_HOME}}, I assume it's
safe to also define {{CASSANDRA_CONF}} in a similar way. Another option would be to load {{cassandra.in.sh}}
before sourcing {{cassandra-env.sh}}, but I don't think this should be necessary because we're
dealing with pre-defined package directories (eg. /usr/share/cassandra and /etc/cassandra),
so it should be safe to define them in a static way.

> 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