hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15222) Use HDR histograms rather than hadoop or yammer's
Date Sat, 06 Feb 2016 00:01:39 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135301#comment-15135301
] 

Elliott Clark commented on HBASE-15222:
---------------------------------------

Longer benchmark run:

{code}
Benchmark                             Mode  Cnt       Score        Error  Units
HistogramBenchmark.testHDRAtomic      avgt   25    4226.755 ±    771.162  ns/op
HistogramBenchmark.testHDRConcurrent  avgt   25    6478.152 ±    275.396  ns/op
HistogramBenchmark.testNormal         avgt   25   15977.900 ±   1076.541  ns/op
HistogramBenchmark.testQuant          avgt   25  223378.087 ± 215236.829  ns/op
{code}

So our Quantile code is soooo slow that it shouldn't be used.
Using HDR's versions of histograms at higher concurrency can half the overhead, or better.

Let me check and see how just yammer's stuff works.

> Use HDR histograms rather than hadoop or yammer's
> -------------------------------------------------
>
>                 Key: HBASE-15222
>                 URL: https://issues.apache.org/jira/browse/HBASE-15222
>             Project: HBase
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.3.0
>
>
> Running the benchmarks now, but it looks like the results are pretty extreme. The locking
in our histograms is pretty extreme.



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

Mime
View raw message