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