You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Mikhail Antonov (JIRA)" <ji...@apache.org> on 2016/10/05 00:37:20 UTC

[jira] [Commented] (HBASE-16146) Counters are expensive...

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

Mikhail Antonov commented on HBASE-16146:
-----------------------------------------

From my perspective (I have not been running YCSB with this patch though) I'm +1 on it for branch-1 and branch-1.3. In some tests/workloads we did see scenarios when excessive thread locals allocations for counters in metrics cause load / latency on the hot machines to go up, impairing stability.

> Counters are expensive...
> -------------------------
>
>                 Key: HBASE-16146
>                 URL: https://issues.apache.org/jira/browse/HBASE-16146
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>         Attachments: HBASE-16146.branch-1.3.001.patch, counters.patch, less_and_less_counters.png
>
>
> Doing workloadc, perf shows 10%+ of CPU being spent on counter#add. If I disable some of the hot ones -- see patch -- I can get 10% more throughput (390k to 440k). Figure something better.



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