[
https://issues.apache.org/jira/browse/CASSANDRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077063#comment-14077063
]
Benedict edited comment on CASSANDRA-7631 at 7/28/14 10:49 PM:
---------------------------------------------------------------
Well, this sort of fits in with an extension I would like to make, which is
in-process stressing (i.e. to avoid going over the network), for which many of
those options would also be meaningless.
I don't see why we couldn't provide a separate shell script that makes some of
the options easier, but I think this makes most sense living directly in stress
itself; we can either ignore, or complain, if unrelated options are set.
was (Author: benedict):
Well, this sort of fits in with an extension I would like to make, which is
in-process stressing (i.e. to avoid going over the network, and if feasible
optionally avoid going through the native protocol), for which many of those
options would also be meaningless.
I don't see why we couldn't provide a separate shell script that makes some of
the options easier, but I think this makes most sense living directly in stress
itself; we can either ignore, or complain, if unrelated options are set.
> 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)
