[
https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1938:
-------------------------
Attachment: caching-keylength-in-kv.patch
Small change to KV. Uses 8 bytes more memory to cache Key Length.
> Make in-memory table scanning faster
> ------------------------------------
>
> Key: HBASE-1938
> URL: https://issues.apache.org/jira/browse/HBASE-1938
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: caching-keylength-in-kv.patch,
> MemStoreScanPerformance.java, test.patch
>
>
> This issue is about profiling hbase to see if I can make hbase scans run
> faster when all is up in memory. Talking to some users, they are seeing
> about 1/4 million rows a second. It should be able to go faster than this
> (Scanning an array of objects, they can do about 4-5x this).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
