hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14921) Memory optimizations
Date Fri, 01 Apr 2016 17:10:25 GMT

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

stack commented on HBASE-14921:

Nice review [~anoop.hbase] On not needing third int, I like the idea of saving on duplication,
but will we always serialize as we do now? In fact, the way we serialize now -- key length
then value length -- is a bit wonky. Should probably just be a long with full Cell length
as first thing in the serialized stream rather than shorts of key and value as we do in KV

I love the idea of saving a whole tier of chunks.

bq. If so, then one Chunk can represent 2^18*2^8=2^26 bytes = 64MB, 

Smaller than 256 bytes? Yes. How'd you get 256 bytes? I didn't follow. Sorry.

bq.  Is it a possible use-case?

It is for analytics-type uses.

> 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
>            Assignee: Anastasia Braginsky
>         Attachments: CellBlocksSegmentInMemStore.pdf, CellBlocksSegmentinthecontextofMemStore(1).pdf,
HBASE-14921-V01.patch, HBASE-14921-V02.patch
> Memory optimizations including compressed format representation and offheap allocations

This message was sent by Atlassian JIRA

View raw message