[
https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938199#comment-14938199
]
Ryan McGuire edited comment on CASSANDRA-10403 at 9/30/15 6:54 PM:
-------------------------------------------------------------------
We enabled the use of different stress branches, so we should be able to run it
now.
I'll restart the job that benedict ran:
http://cstar.datastax.com/tests/id/01b714d8-5f32-11e5-a4e4-42010af0688f
I'll use [~benedict]'s stress branch from:
https://github.com/belliottsmith/cassandra/tree/stress-report-interval
EDIT: test started:
http://cstar.datastax.com/tests/id/ac36457a-67a0-11e5-8666-42010af0688f
was (Author: enigmacurry):
We enabled the use of different stress branches, so we should be able to run it
now.
I'll restart the job that benedict ran:
http://cstar.datastax.com/tests/id/01b714d8-5f32-11e5-a4e4-42010af0688f
I'll use [~benedict]'s stress branch from:
https://github.com/belliottsmith/cassandra/tree/stress-report-interval
> 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)
