[
https://issues.apache.org/jira/browse/CASSANDRA-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252767#comment-14252767
]
Jonathan Shook commented on CASSANDRA-8503:
-------------------------------------------
[~benedict]
Unless I am mistaken, you are describing an issue in the data generation of
stress as a reason to not do a meaningful time series sanity check in CI. My
gut feeling on what might qualify as 'sufficiently close' is that we probably
differ on the details. I'd be much more satisfied with a realistic test. I
might be convinced that specific tweaks would make the test more sensitive than
the target scenario, which would be ideal.
I'm not sure what the complexity of fixing #7980 is, but it seems more of a
structural limitation than a functional one. I'm keenly interested in seeing
these tests come to life. If it helps, I can provide a tool to drive load for
time series testing.
> 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)
