[
https://issues.apache.org/jira/browse/CASSANDRA-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250811#comment-14250811
]
Benedict commented on CASSANDRA-8503:
-------------------------------------
[~jshook] I think we can model a timeseries workload sufficiently closely
already (it won't be identical, but it will behave the same - no doubt some
minor tweaks can make it feel closer), the only problem is the generation of
large partitions with only a single clustering column is currently very
inefficient. See CASSANDRA-7980.
> Collect important stress profiles for regression analysis done by jenkins
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-8503
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8503
> Project: Cassandra
> Issue Type: Task
> Reporter: Ryan McGuire
> Assignee: Ryan McGuire
> Attachments: inmemory.yaml, ycsb.yaml
>
>
> We have a weekly job setup on CassCI to run a performance benchmark against
> the dev branches as well as the last stable releases.
> Here's an example:
> http://cstar.datastax.com/tests/id/8223fe2e-8585-11e4-b0bf-42010af0688f
> This test is currently pretty basic, it's running on three nodes, with a the
> default stress profile. We should crowdsource a collection of stress profiles
> to run, and then once we have many of these tests running we can collect them
> all into a weekly email.
> Ideas:
> * Timeseries (Can this be done with stress? not sure)
> * compact storage
> * compression off
> * ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
