cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-10403) Consider reverting to CMS GC on 3.0
Date Wed, 14 Oct 2015 13:58:06 GMT

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

T Jake Luciani edited comment on CASSANDRA-10403 at 10/14/15 1:57 PM:
----------------------------------------------------------------------

bq. Do package installs need any tweaking to support the jvm.options file or anything in the
/conf dir is already supported?

The new jvm.options file needs to be added to debian/cassandra.install


was (Author: tjake):
bq. Do package installs need any tweaking to support the jvm.options file or anything in the
/conf dir is already supported?

No the package installs just use the -env.sh file directly

> 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