[
https://issues.apache.org/jira/browse/CASSANDRA-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297421#comment-15297421
]
Nitsan Wakart commented on CASSANDRA-11853:
-------------------------------------------
Can you give more details? ops/sec? number of threads? does the data agree with
-XX:+PrintGCApplicationStoppedTime for instance?
CO can definitely account for these differences, you can use the hdr log to get
the response vs. service vs. wait time breakdown (and correlate the pauses to
the GC log etc).
> 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)
