[
https://issues.apache.org/jira/browse/HBASE-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549859#comment-14549859
]
Lars Hofhansl commented on HBASE-13448:
---------------------------------------
What about key length? Not all Cells will have a notion of a key length, I
thought we're going to get rid of it (rather than now cementing its use more by
caching the key length).
Are there some perf numbers (single machine is fine)? Or else we're flying
blind (Apologies if I missed them. What I see from the comments here is s 2-3%
perf improvement at the expense of 15% of young GC, am I reading that
correctly?)
> New Cell implementation with cached component offsets/lengths
> -------------------------------------------------------------
>
> Key: HBASE-13448
> URL: https://issues.apache.org/jira/browse/HBASE-13448
> Project: HBase
> Issue Type: Sub-task
> Components: Scanners
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 2.0.0
>
> Attachments: HBASE-13448.patch, HBASE-13448_V2.patch,
> HBASE-13448_V3.patch, gc.png, hits.png
>
>
> This can be extension to KeyValue and can be instantiated and used in read
> path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
