Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6F174200BDD for ; Sat, 5 Nov 2016 01:05:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6DDCC160AFE; Sat, 5 Nov 2016 00:05:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B3199160B04 for ; Sat, 5 Nov 2016 01:05:00 +0100 (CET) Received: (qmail 20851 invoked by uid 500); 5 Nov 2016 00:04:59 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 20782 invoked by uid 99); 5 Nov 2016 00:04:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Nov 2016 00:04:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9CBFE2C1F56 for ; Sat, 5 Nov 2016 00:04:59 +0000 (UTC) Date: Sat, 5 Nov 2016 00:04:59 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17016) Reimplement per-region latency histogram metrics MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 05 Nov 2016 00:05:01 -0000 [ https://issues.apache.org/jira/browse/HBASE-17016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15638127#comment-15638127 ] Enis Soztutar commented on HBASE-17016: --------------------------------------- bq. If we can bring them back, and they are cheap - sure, why not. Fair enough. bq. If we find out that any latency histograms are relatively expensive (in some visible form) I'd be in favor or removing them, unless someone has the usecase when they are actually useful. I think the findings at HBASE-17017 justifies the removal, other than object allocation, there is 17% perf boost with basic testing. We can only bring them back if we do the same test with a new patch and there is no impact for the same test (both object allocation, and perf impact). > Reimplement per-region latency histogram metrics > ------------------------------------------------ > > Key: HBASE-17016 > URL: https://issues.apache.org/jira/browse/HBASE-17016 > Project: HBase > Issue Type: Task > Components: metrics > Affects Versions: 2.0.0, 1.4.0 > Reporter: Andrew Purtell > Fix For: 2.0.0, 1.4.0 > > > Follow up from HBASE-10656, where [~enis] says: > {quote} > the main problem is that we have A LOT of per-region metrics that are latency histograms. These latency histograms create many many Counter / LongAdder objects. We should get rid of per-region latencies and maybe look at reducing the per-region metric overhead. > {quote} > And [~ghelmling] gives us a good candidate to implement pre-region latency histograms [HdrHistogram|https://github.com/HdrHistogram/HdrHistogram]. > Let's consider removing the per-region latency histograms and reimplement using HdrHistogram. -- This message was sent by Atlassian JIRA (v6.3.4#6332)