[jira] [Comment Edited] (CASSANDRA-7918) Provide graphing tool along with cassandra-stress

["Ryan McGuire (JIRA)" <ji...@apache.org>]

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

Ryan McGuire edited comment on CASSANDRA-7918 at 11/24/14 3:21 AM:
-------------------------------------------------------------------

I've made more progress on this, everything from my spec above is now [implemented on my branch|https://github.com/EnigmaCurry/cassandra/tree/7918-stress-graph]. 

One bug so far is when you don't specify a thread count for reads, it doesn't know how to parse the multiple iterations at different thread counts (it mashes them all together into one graph). As long as you specify the thread count your fine.

Here's a test I ran:

{code}
cassandra-stress write n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test1
cassandra-stress read n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test1

cassandra-stress write n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test2
cassandra-stress read n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test2

cassandra-stress write n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test3
cassandra-stress read n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test3
{code} 

And it produced this single 282K html file:

http://ryanmcguire.info/ds/jira/test7918.html




was (Author: enigmacurry):
I've made more progress on this, everything from my spec above is now [implemented on my branch|https://github.com/EnigmaCurry/cassandra/tree/7918-stress-graph]. 

One bug so far is when you don't specify a thread count for reads, it doesn't know how to parse the multiple iterations at different thread counts (it mashes them all together into one graph). As long as you specify the thread count your fine.

Here's a test I ran:

{code}
./tools/bin/cassandra-stress write n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test1
./tools/bin/cassandra-stress read n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test1

./tools/bin/cassandra-stress write n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test2
./tools/bin/cassandra-stress read n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test2

./tools/bin/cassandra-stress write n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test3
./tools/bin/cassandra-stress read n=1000000 -rate threads=100 -graph file=test7918.html title=test revision=test3
{code} 

And it produced this single 282K html file:

http://ryanmcguire.info/ds/jira/test7918.html



> Provide graphing tool along with cassandra-stress
> -------------------------------------------------
>
>                 Key: CASSANDRA-7918
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7918
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Benedict
>            Assignee: Ryan McGuire
>            Priority: Minor
>
> Whilst cstar makes some pretty graphs, they're a little limited and also require you to run your tests through it. It would be useful to be able to graph results from any stress run easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)