[
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902754#comment-14902754
]
Benedict commented on CASSANDRA-7486:
-------------------------------------
Get this running on blade_11b...
{code}
raceback (most recent call last):
File "/home/ryan/git/cstar_perf/env/bin/cstar_perf_stress", line 9, in
<module>
load_entry_point('cstar-perf.tool==1.0', 'console_scripts',
'cstar_perf_stress')()
File "/home/ryan/git/cstar_perf/tool/cstar_perf/tool/stress_compare.py", line
258, in main
stress_compare(**cfg)
File "/home/ryan/git/cstar_perf/tool/cstar_perf/tool/stress_compare.py", line
111, in stress_compare
stress_shas = setup_stress(stress_revisions)
File "/home/ryan/git/cstar_perf/tool/cstar_perf/tool/benchmark.py", line 406,
in setup_stress
revisions.update(build_stress(stress_revision))
File "/home/ryan/git/cstar_perf/tool/cstar_perf/tool/benchmark.py", line 382,
in build_stress
raise AssertionError('Invalid stress_revision: {}'.format(stress_revision))
AssertionError: Invalid stress_revision: enigmacurry/stress-report-interval
{code}
Is the new code only deployed to blade_11, perhaps?
> Migrate to G1GC by default
> --------------------------
>
> Key: CASSANDRA-7486
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7486
> Project: Cassandra
> Issue Type: New Feature
> Components: Config
> Reporter: Jonathan Ellis
> Fix For: 3.0 alpha 1
>
>
> See
> http://www.slideshare.net/MonicaBeckwith/garbage-first-garbage-collector-g1-7486gc-migration-to-expectations-and-advanced-tuning
> and https://twitter.com/rbranson/status/482113561431265281
> May want to default 2.1 to G1.
> 2.1 is a different animal from 2.0 after moving most of memtables off heap.
> Suspect this will help G1 even more than CMS. (NB this is off by default but
> needs to be part of the test.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
