Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 30 Sep 2014 06:37:34 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12744825.1412035899000.152536.1412059054428@Atlassian.JIRA>
In-Reply-To: <JIRA.12744825.1412035899000@Atlassian.JIRA>
References: <JIRA.12744825.1412035899000@Atlassian.JIRA>
 <JIRA.12744825.1412035899680@arcas>
Subject: [jira] [Commented] (HBASE-12116) Hot contention spots; writing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-12116:
-------------------------------

[~eclark] Sample was for 5 minutes.  There is a small bit of getting values from configuration which does getProperty but main culprit here is not very interesting... its stringifying exceptions (Was throwing loads of NSRE around sample time).  Let me get a better sampling.

This tool seems to do better job reporting CPU use, or at least, agrees that CRC is the main consumer of CPU as per our flame graph experiments.  Hopefully its good reporting contention. Has a dtrace plugin.  Let me see if can get that to work....


> Hot contention spots; writing
> -----------------------------
>
>                 Key: HBASE-12116
>                 URL: https://issues.apache.org/jira/browse/HBASE-12116
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>         Attachments: Screen Shot 2014-09-29 at 5.12.51 PM.png
>
>
> Playing with flight recorder, here are some write-time contentious synchronizations/locks (picture coming)


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