Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 16 Jan 2015 11:15:34 +0000 (UTC)
From: "Sam Tunnicliffe (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12767771.1421338936000.100989.1421406934959@Atlassian.JIRA>
In-Reply-To: <JIRA.12767771.1421338936000@Atlassian.JIRA>
References: <JIRA.12767771.1421338936000@Atlassian.JIRA>
 <JIRA.12767771.1421338936678@arcas>
Subject: [jira] [Updated] (CASSANDRA-8627) Support Total/Recent latency
 histogram metrics for range slices
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-8627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sam Tunnicliffe updated CASSANDRA-8627:
---------------------------------------
    Attachment: 8627.txt

> Support Total/Recent latency histogram metrics for range slices
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-8627
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8627
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Lohfink
>            Assignee: Sam Tunnicliffe
>              Labels: metrics
>             Fix For: 2.1.3
>
>         Attachments: 8627.txt
>
>
> The Metrics histogram is pretty bad at non-normal data like latencies and (empirically tested and theoretically) is untrustworthy at 99th percentile. For applications that care about the percentiles having the more statistically accurate version is beneficial.  Adding the deprecated methods like other latency histograms for CASSANDRA-7338 temporarily would help.
> This is just for 2.1 branch. CASSANDRA-5657 solves everything in 3.0.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)