You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2016/02/25 18:47:18 UTC

[jira] [Comment Edited] (HBASE-14921) Memory optimizations

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

Anoop Sam John edited comment on HBASE-14921 at 2/25/16 5:46 PM:
-----------------------------------------------------------------

So after the in memory flush, the CellBlockSegment will be an array of Cells (?) Or array of BBs, allocated from MSLAB?
 A cell from memstore (CSLM) when moved to CellBlockSegment, we will need copy the Cell bytes into new MSLAB area and recreate Cell?
How we will know this array's size before hand?  When an active memstore segment is flushed in memory, we may be able to remove some of these cells?(version expired and all). I think the initial use case mentioned in the 1st issue was this.  Am I missing some thing?


was (Author: anoop.hbase):
So after the in memory flush, the CellBlockSegment will be an array of Cells (?) A cell from memstore (CSLM) when moved to CellBlockSegment, we will need copy the Cell bytes into new MSLAB area and recreate Cell?

> Memory optimizations
> --------------------
>
>                 Key: HBASE-14921
>                 URL: https://issues.apache.org/jira/browse/HBASE-14921
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: Eshcar Hillel
>
> Memory optimizations including compressed format representation and offheap allocations



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)