cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7918) Provide graphing tool along with cassandra-stress
Date Wed, 22 Jul 2015 16:37:05 GMT


Benedict commented on CASSANDRA-7918:

I'm not sure my opinion should carry as much weight here, however I'll restate what I've said
privately: my concern is that this has languished for getting on for a year, and if we commit
without improving the graphs the little pressure there is will vanish, and we'll all make
do for another year or more. Committing doesn't buy the _project_ much, but getting better
graphs sooner buys it quite a lot. Not committing perhaps costs the users who would like this
now a little, but potentially buys them the better decision making of improved graphs sooner
in trade. 

To me that makes delay a net win, but that's only my finger in air wild assumptions. 

TL;DR: I'd prefer we harnessed the little pressure we're getting for this, by delaying commit
until we can improve the graphs, so we're encouraged to do so sooner.

Either that or we commit as is and assign somebody the task of improving the graphs, and they
commit to delivering them within the next two months (meaning we may get them before christmas
:)), say.

> Provide graphing tool along with cassandra-stress
> -------------------------------------------------
>                 Key: CASSANDRA-7918
>                 URL:
>             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

View raw message