Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DC550187D5 for ; Fri, 18 Dec 2015 00:27:47 +0000 (UTC) Received: (qmail 65728 invoked by uid 500); 18 Dec 2015 00:27:47 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 65596 invoked by uid 500); 18 Dec 2015 00:27:47 -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 65554 invoked by uid 99); 18 Dec 2015 00:27:47 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2015 00:27:47 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D52632C1F8B for ; Fri, 18 Dec 2015 00:27:46 +0000 (UTC) Date: Fri, 18 Dec 2015 00:27:46 +0000 (UTC) From: "Sean Busbey (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-14205) RegionCoprocessorHost System.nanoTime() performance bottleneck MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-14205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-14205: -------------------------------- Component/s: Performance > RegionCoprocessorHost System.nanoTime() performance bottleneck > -------------------------------------------------------------- > > Key: HBASE-14205 > URL: https://issues.apache.org/jira/browse/HBASE-14205 > Project: HBase > Issue Type: Bug > Components: Coprocessors, Performance, regionserver > Reporter: Jan Van Besien > Assignee: Andrew Purtell > Priority: Critical > Fix For: 2.0.0, 1.2.0, 1.3.0 > > Attachments: HBASE-14205.patch > > > The tracking of execution time of coprocessor methods introduced in HBASE-11516 introduces 2 calls to System.nanoTime() per coprocessor method per coprocessor. This is resulting in a serious performance bottleneck in certain scenarios. > For example consider the scenario where many rows are being ingested (PUT) in a table which has multiple coprocessors (we have up to 20 coprocessors). This results in 8 extra calls to System.nanoTime() per coprocessor (prePut, postPut, postStartRegionOperation and postCloseRegionOperation) which has in total (i.e. times 20) been seen to result in a 50% increase of execution time. > I think it is generally considered bad practice to measure execution times on such a small scale (per single operation). Also note that measurements are taken even for coprocessors that do not even have an actual implementation for certain operations, making the problem worse. -- This message was sent by Atlassian JIRA (v6.3.4#6332)