You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2015/04/16 05:03:58 UTC

[jira] [Commented] (HBASE-13448) New Cell implementation with cached component offsets/lengths

    [ https://issues.apache.org/jira/browse/HBASE-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497494#comment-14497494 ] 

ramkrishna.s.vasudevan commented on HBASE-13448:
------------------------------------------------

Ya 2-3 % max is what we would get. Atleast the hot spot would not be cribbing in the Bytes.toXXX call in these APIs.
But just curious, why is GC increasing because of this? Am not able to relate. May be am missing something.

> 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)