[ 
https://issues.apache.org/jira/browse/HADOOP-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558365#action_12558365
 ] 

Hadoop QA commented on HADOOP-2533:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12373037/2533-v3.patch
against trunk revision r611537.

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

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1567/testReport/
Findbugs warnings: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1567/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1567/artifact/trunk/build/test/checkstyle-errors.html
Console output: 
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1567/console

This message is automatically generated.

> [hbase] Performance: Scanning, just creating MapWritable in next consumes 
> >20% CPU
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2533
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2533
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: contrib/hbase
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>             Fix For: 0.16.0
>
>         Attachments: 2533-v2.patch, 2533-v3.patch, 2533.patch, dirty.patch
>
>
> Every call to HScanner.next creates an instance of MapWritable.  MapWritables 
> are expensive.  Watching a scan run in the profiler, the setup of the 
> MapWritable -- filling out the idToClassMap and classToIdMap -- consumes 20% 
> of all CPU.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to