hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2533) [hbase] Performance: Scanning, just creating MapWritable in next consumes >20% CPU
Date Sun, 13 Jan 2008 03:56:33 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HADOOP-2533:
--------------------------

    Status: In Progress  (was: Patch Available)

Hudson queue is empty.  Try requeuing to see if that'll get an entry in the queue.

> [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.


Mime
View raw message