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

Joshua McKenzie commented on CASSANDRA-7918:
--------------------------------------------

Given our recent regressions and the upcoming effort for a performance testing 
harness, we need to move on this.

Right now we have 1) Benedict's option that has more information but that's 
written using gnuplot which people feel strongly against and 2) Ryan's option 
that has less information available but is perhaps more immediately / 
intuitively digestible and doesn't use gnuplot.

[~enigmacurry]: what are the chances you could integrate the 
throughput/latency/gc and tri-graphing approach benedict took into the existing 
cstar framework, giving us the best of both worlds? I wouldn't mind seeing the 
current format of the #'s from your solution below the graphs.

One other thing - we need to scrape the cassandra.yaml file and dump out the 
relevant settings used for the test (or perhaps just all of them at the outset) 
as well as snapshotting the specific cassandra-stress command used to generate 
the test results for reproduction. A SHA for commit used on the test would also 
help, and I think that would give us a solid initial framework to start testing 
with and have reproducible tests.

We can pursue future additions onto this later (capturing system info, 
/proc/cpuinfo, etc) but there's no point in holding it up to get it to be 
perfect for our 1st revision.


> 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
>         Attachments: 7918.patch, reads.svg
>
>
> 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)

Reply via email to