[
https://issues.apache.org/jira/browse/CASSANDRA-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583891#comment-14583891
]
Joshua McKenzie commented on CASSANDRA-7918:
--------------------------------------------
I think the general concern is that maintaining a code-base with gnuplot in it
isn't something your fellow contributors are thrilled about, not the potential
difficulty of a user interacting with it.
How about something like a verbose_stress.sh that dumps current commit sha,
yaml settings, and stress args to a file, passes all args through to
cassandra-stress.* and appends the stress output to that file, then compresses
the final results to the an archive named w/datetime stamp? Some simple section
delimiters and our graph generator could parse that trivially.
Avoids the coupling w/stress, keeps the collection of metadata and test output
as a separate logical entity, and we get our canonical source of truth.
> 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)
