[ 
https://issues.apache.org/jira/browse/CASSANDRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077457#comment-14077457
 ] 

Benedict commented on CASSANDRA-7631:
-------------------------------------

Separately, prior to 2.1.0 is probably the best time to bikeshed syntax on the 
current version. Since we now have some actual users, it might be worth filing 
a ticket for people to bikeshed their proposed syntax improvements and if 
they're easily achieved we can sneak them in (or into 2.1.1 since this is only 
a tool). When this was introduced there wasn't really any discussion of the 
syntax because of a general lack of interest. Now people have used the tool 
maybe there are some good suggestions. If anyone has any, file the ticket which 
can be a lightning rod for other suggestions.

> 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
(v6.2#6252)

Reply via email to