[
https://issues.apache.org/jira/browse/CASSANDRA-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156724#comment-14156724
]
Ryan McGuire commented on CASSANDRA-7918:
-----------------------------------------
Here's how I'm planning on attacking this
* I've refactored my original graph tool from cstar_perf into a single HTML
file (includes embedded jQuery, d3js, and other dependencies.) - [example
here|http://static.enigmacurry.com/tmp/cstar_perf_graph_standalone.html]
* Add a new option to stress called *-graph*
** *-graph* takes a required parameter *file=* to specify the HTML report file
to generate.
** Stress will record the metrics it collects (intervals) to a temporary file.
** When done, it will write out the HTML with the intervals converted into a
JSON format embedded inside.
** If the file already exists, it will first load the existing JSON data and
merge it with the new data (which adds these new operations to the dropdown as
it goes.)
** Originally, this tool was meant to compare two or more different
configurations, so we can retain that behavior by adding an optional parameter
to *-graph* called *revision=*. Revision is just a unique name to give to your
particular cluster configuration. This revision can be reused on multiple runs
and a new metrics will be merged into the JSON for that revision as described
above.
** Cleanup of temporary metric file.
Example to run a write, then a read, on two different clusters, generating a
single report to compare the two:
{code}
# First cluster:
cassandra-stress write n=19000000 -node cluster1 -graph
file=compare_clusters.html revision=cluster1
cassandra-stress read n=19000000 -node cluster1 -graph
file=compare_clusters.html revision=cluster1
# Second cluster:
cassandra-stress write n=19000000 -node cluster2 -graph
file=compare_clusters.html revision=cluster2
cassandra-stress read n=19000000 -node cluster2 -graph
file=compare_clusters.html revision=cluster2
{code}
The resulting compare_clusters.html will contain all four runs and the file can
be loaded into any modernish web browser, no webserver, nor internet connection
required.
> 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)
