Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 30 Apr 2012 20:43:49 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <944388305.10788.1335818629270.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <399335940.7048.1335666288507.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5897) prePut coprocessor hook causing
 substantial CPU usage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-5897:
--------------------------------------

Looked over Todd's patch. The only difference is that before the prePut's edits ended up in WALEdit before the family edits. Now that is reversed. Not sure if that even makes a difference. +1 otherwise
                
> prePut coprocessor hook causing substantial CPU usage
> -----------------------------------------------------
>
>                 Key: HBASE-5897
>                 URL: https://issues.apache.org/jira/browse/HBASE-5897
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.92.2, 0.94.0, 0.96.0
>
>         Attachments: 5897-simple.txt, hbase-5897.txt
>
>
> I was running an insert workload against trunk under oprofile and saw that a significant portion of CPU usage was going to calling the "prePut" coprocessor hook inside doMiniBatchPut, even though I don't have any coprocessors installed. I ran a million-row insert and collected CPU time spent in the RS after commenting out the preput hook, and found CPU usage reduced by 33%.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira