Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4111319D92 for ; Fri, 1 Apr 2016 17:10:26 +0000 (UTC) Received: (qmail 70574 invoked by uid 500); 1 Apr 2016 17:10:26 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 70528 invoked by uid 500); 1 Apr 2016 17:10:25 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 70503 invoked by uid 99); 1 Apr 2016 17:10:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2016 17:10:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8DACC2C1F6A for ; Fri, 1 Apr 2016 17:10:25 +0000 (UTC) Date: Fri, 1 Apr 2016 17:10:25 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-14921) Memory optimizations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 now. 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 (v6.3.4#6332)