[
https://issues.apache.org/jira/browse/HBASE-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497582#comment-14497582
]
Anoop Sam John commented on HBASE-13448:
----------------------------------------
Even when we parse int/long from KV's byte[] Unsafe utils are being used. So
those were not too costly. This would better help when we do HBASE-10800 and
ServerCell jira as there will be more calls to getXXXOffset and getXXXLengths
then. Ya certain items like ts ( 8 bytes save) can be avoided from cache.
As long as the bigger size are short living and young GC itself can clean them,
we need worry much? The increase in GC is the young GC activity only ?
> 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
> Attachments: HBASE-13448.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)
