[
https://issues.apache.org/jira/browse/CASSANDRA-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302493#comment-15302493
]
T Jake Luciani commented on CASSANDRA-11853:
--------------------------------------------
Thanks!
I re-ran some differing runs against stress and your branch the results look
reasonable:
Slightly higher latencies in the throttle case but likely due to the fact we
are no longer sampling
http://cstar.datastax.com/graph?command=one_job&stats=94d03982-2356-11e6-a5b1-0256e416528f&metric=op_rate&operation=3_read&smoothing=1&show_aggregates=true&xmin=0&xmax=550&ymin=0&ymax=123449.7
I've squashed and rebased branch and kicked off tests:
[squashed branch|https://github.com/tjake/cassandra/tree/co-correction]
[testall|http://cassci.datastax.com/job/tjake-co-correction-testall/]
[dtest|http://cassci.datastax.com/job/tjake-co-correction-dtest/]
> Improve Cassandra-Stress latency measurement
> --------------------------------------------
>
> Key: CASSANDRA-11853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11853
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Nitsan Wakart
> Assignee: Nitsan Wakart
> Fix For: 3.x
>
>
> Currently CS reports latency using a sampling latency container and reporting
> service time (as opposed to response time from intended schedule) leading to
> coordinated omission.
> Fixed here:
> https://github.com/nitsanw/cassandra/tree/co-correction
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
