Benedict commented on CASSANDRA-7631:

I'd be inclined to keep this feature for user commands only, to keep 
maintenance complexity down. The writing is on the wall for the legacy mode 
anyway, for anything other than a very quick benchmark of general server 
performance. I don't see a reason to build the sstables up in advance for that 
kind of use case.

> Allow Stress to write directly to SSTables
> ------------------------------------------
>                 Key: CASSANDRA-7631
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7631
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Russell Alexander Spitzer
>            Assignee: Russell Alexander Spitzer
> One common difficulty with benchmarking machines is the amount of time it 
> takes to initially load data. For machines with a large amount of ram this 
> becomes especially onerous because a very large amount of data needs to be 
> placed on the machine before page-cache can be circumvented. 
> To remedy this I suggest we add a top level flag to Cassandra-Stress which 
> would cause the tool to write directly to sstables rather than actually 
> performing CQL inserts. Internally this would use CQLSStable writer to write 
> directly to sstables while skipping any keys which are not owned by the node 
> stress is running on. The same stress command run on each node in the cluster 
> would then write unique sstables only containing data which that node is 
> responsible for. Following this no further network IO would be required to 
> distribute data as it would all already be correctly in place.

This message was sent by Atlassian JIRA

Reply via email to