[
https://issues.apache.org/jira/browse/CASSANDRA-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler resolved CASSANDRA-6681.
---------------------------------------
Resolution: Fixed
-rate and (I think) pretty complete usage help on all options was included in
2.1 stress changes - not sure why this ticket remained open after the comment
above.
{noformat}
(cassandra-2.1)mshuler@hana:~/git/cassandra$ cassandra-stress help -rate
Usage: -rate threads=? [limit=?]
OR
Usage: -rate [auto] [threads>=?] [threads<=?]
threads=? run this many clients concurrently
limit=? (default=0/s) limit operations per second across
all clients
auto test with increasing number of
threadCount until performance plateaus
threads>=? (default=4) run at least this many clients
concurrently
threads<=? (default=1000) run at most this many clients
concurrently
{noformat}
> Update cassandra-stress README
> ------------------------------
>
> Key: CASSANDRA-6681
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6681
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Matt Stump
> Priority: Minor
> Labels: lhf
>
> The cassandra-stress README hasn't been updated to reflect the recent work in
> the 2.x releases. Additionally, no example is given in the help string that
> demonstrates how to use various parameters. For example no input format is
> given for the "-rate" parameter. It could be threads>=N, threads=n, limit=N
> etc..
--
This message was sent by Atlassian JIRA
(v6.2#6252)
