[ https://issues.apache.org/jira/browse/HBASE-14869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031322#comment-15031322 ]
Lars Hofhansl commented on HBASE-14869: --------------------------------------- -v3 looks good to me. I wonder whether it's worth to make it more generic. I.e. have one class and pass unit and ranges in? Maybe overkill. Need a matching Hadoop1 change for 0.98 (or we can leave Hadoop1 as is, [~apurtell]?), and a version for the master branch. I'd also like to get input from other folks about whether there any preferences for the metrics names ([~davelatham], [~stack], [~enis], any opinions). > 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: Vikas Vishwakarma > Attachments: 14869-test-0.98.txt, 14869-v1-0.98.txt, > 14869-v2-0.98.txt, 14869-v3-0.98.txt, AppendSizeTime.png, Get.png > > > 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)