Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 May 2016 00:28:12 +0000 (UTC)
From: "Nitsan Wakart (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12971528.1463752311000.272191.1464049692835@Atlassian.JIRA>
In-Reply-To: <JIRA.12971528.1463752311000@Atlassian.JIRA>
References: <JIRA.12971528.1463752311000@Atlassian.JIRA> <JIRA.12971528.1463752311080@arcas>
Subject: [jira] [Commented] (CASSANDRA-11853) Improve Cassandra-Stress
 latency measurement
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 24 May 2016 00:28:14 -0000


    [ 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)