[
https://issues.apache.org/jira/browse/CASSANDRA-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350791#comment-14350791
]
Benedict commented on CASSANDRA-8929:
-------------------------------------
Once we're sampling, we're essentially producing stress profiles (or an
analogue), no? At that point I'm not sure we buy much by introducing complexity
into the codebase. The set of possible scenarios isn't gigantic, and it seems
we can produce it by manual analysis and curation of a set of workloads we care
about, i.e. CASSANDRA-8503.
There are a raft of stress tickets open to improve its capabilities to support
completely arbitrary workloads, but it might be preferably to complicating c*
itself.
> Workload sampling
> -----------------
>
> Key: CASSANDRA-8929
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8929
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jonathan Ellis
>
> Workload *recording* looks to be unworkable (CASSANDRA-6572). We could build
> something almost as useful by sampling the requests sent to a node and
> building a synthetic workload with the same characteristics using the same
> (or anonymized) schema.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
