You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "sankalp kohli (JIRA)" <ji...@apache.org> on 2015/08/30 07:44:46 UTC
[jira] [Commented] (CASSANDRA-8929) Workload sampling
[ https://issues.apache.org/jira/browse/CASSANDRA-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14721400#comment-14721400 ]
sankalp kohli commented on CASSANDRA-8929:
------------------------------------------
We are also looking at doing something very similar so this feature will be of great help. It will be a good start to to record the traffic but we should also try to find a way to find something about the existing data. A simple select statement on a small CQL partition will be very different from the one on large CQL partition in terms of load on C*.
We should try to find a way to deal with this as well ideally.... may be as a different JIRA. (I am not sure if someone also mentioned this before in the comments)
> 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
> Assignee: Robert Stupp
>
> 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)