[
https://issues.apache.org/jira/browse/HBASE-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552177#comment-14552177
]
Anoop Sam John commented on HBASE-13448:
----------------------------------------
Seeing the number of times the getKeyLength() call happens and the decoding of
the keylength, I feel we have to cache that also. I can see this keylength
decoding is required while getting length/offset like qualifier. The calls to
these will be more as we do other cleanup (mentioned by Stack) While we did
profiling with offheap work and patch, we saw this getKeyLength() also in hot
path.
> 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: 13291-0.98.txt, 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)
