Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A9E86200B29 for ; Thu, 16 Jun 2016 05:52:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A8806160A57; Thu, 16 Jun 2016 03:52:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9027B160A4D for ; Thu, 16 Jun 2016 05:52:06 +0200 (CEST) Received: (qmail 68322 invoked by uid 500); 16 Jun 2016 03:52:05 -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 68276 invoked by uid 99); 16 Jun 2016 03:52:05 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2016 03:52:05 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 503452C1F6A for ; Thu, 16 Jun 2016 03:52:05 +0000 (UTC) Date: Thu, 16 Jun 2016 03:52:05 +0000 (UTC) From: "Mikhail Antonov (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-15950) Fix memstore size estimates to be more tighter MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 16 Jun 2016 03:52:07 -0000 [ https://issues.apache.org/jira/browse/HBASE-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333016#comment-15333016 ] Mikhail Antonov commented on HBASE-15950: ----------------------------------------- [~enis] the last two sentences of the release note makes me somewhat uncomfortable to get it in as is... That sounds like if I do drop-in replacement w/o config re-testing for some non-trivial workloads it could likely break? I think we don't expect people to re-tune their memory settings and traffic when updating to minor release. I'm thinking we would either just not port it to 1.3, or make it disabled by default in 1.3 with option to enable, not the other way around. > Fix memstore size estimates to be more tighter > ---------------------------------------------- > > Key: HBASE-15950 > URL: https://issues.apache.org/jira/browse/HBASE-15950 > Project: HBase > Issue Type: Bug > Reporter: Enis Soztutar > Assignee: Enis Soztutar > Fix For: 2.0.0, 1.4.0 > > Attachments: Screen Shot 2016-06-02 at 8.48.27 PM.png, hbase-15950-v0.patch, hbase-15950-v1.patch, hbase-15950-v2.branch-1.patch, hbase-15950-v2.branch-1.patch, hbase-15950-v2.patch > > > While testing something else, I was loading a region with a lot of data. Writing 30M cells in 1M rows, with 1 byte values. > The memstore size turned out to be estimated as 4.5GB, while with the JFR profiling I can see that we are using 2.8GB for all the objects in the memstore (KV + KV byte[] + CSLM.Node + CSLM.Index). > This obviously means that there is room in the write cache that we are not effectively using. -- This message was sent by Atlassian JIRA (v6.3.4#6332)