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

Hadoop QA commented on HBASE-5897:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12525125/testRegionServerCoprocessorExceptionWithRemove.stack
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 6 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/1697//console

This message is automatically generated.
                
> 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, 
> testRegionServerCoprocessorExceptionWithRemove.stack
>
>
> 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

        

Reply via email to