[
https://issues.apache.org/jira/browse/CASSANDRA-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297435#comment-15297435
]
T Jake Luciani commented on CASSANDRA-11853:
--------------------------------------------
The runs I did are here:
http://cstar.datastax.com/graph?command=one_job&stats=022678d8-2123-11e6-bcd7-0256e416528f&metric=95th_latency&operation=3_read&smoothing=1&show_aggregates=true&xmin=0&xmax=549.67&ymin=0&ymax=294.36
bq. could you clarify what you mean by that?
I mean with throttle=100000/s a throttle is required to account for C.O.
bq. Can you give more details? ops/sec? number of threads?
100k/sec with 500 threads. Unthrottled it was > 200k so my guess is if I lower
the threads the latencies will go down. I will try running with a few
different scenarios.
> 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)
