hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13448) New Cell implementation with cached component offsets/lengths
Date Thu, 16 Apr 2015 03:03:58 GMT

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

Mime
View raw message