You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2008/01/10 01:02:34 UTC

[jira] Commented: (HADOOP-2533) [hbase] Performance: Scanning, just creating MapWritable in next consumes >20% CPU

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

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

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

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

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

Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1531/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
>            Priority: Minor
>             Fix For: 0.16.0
>
>         Attachments: 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.