[
https://issues.apache.org/jira/browse/HBASE-14869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028244#comment-15028244
]
Lars Hofhansl commented on HBASE-14869:
---------------------------------------
Hmm... Looking at all the metrics, I also see metrics like: ResponseSize,
RequestSize, AppendSize, etc. Those also get the ranges now, which doesn't make
sense (the numbers mean bytes, not ms), in the end we'll want the same there
(byte 90'iles cannot be combined either, but we'd want different ranges there I
assume).
So I might have to invent a new metric type for this. Something like
MutableTimeHistogram.
> Better request latency histograms
> ---------------------------------
>
> Key: HBASE-14869
> URL: https://issues.apache.org/jira/browse/HBASE-14869
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Attachments: 14869-test-0.98.txt, 14869-v1-0.98.txt
>
>
> I just discussed this with a colleague.
> The get, put, etc, histograms that each region server keeps are somewhat
> useless (depending on what you want to achieve of course), as they are
> aggregated and calculated by each region server.
> It would be better to record the number of requests in certainly latency
> bands in addition to what we do now.
> For example the number of gets that took 0-5ms, 6-10ms, 10-20ms, 20-50ms,
> 50-100ms, 100-1000ms, > 1000ms, etc. (just as an example, should be
> configurable).
> That way we can do further calculations after the fact, and answer questions
> like: How often did we miss our SLA? Percentage of requests that missed an
> SLA, etc.
> Comments?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
