Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1925772992.1217109871679.JavaMail.jira@brutus>
Date: Sat, 26 Jul 2008 15:04:31 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-779) Test changing
 hbase.hregion.memcache.block.multiplier to 2
In-Reply-To: <935937494.1217097631715.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-779:
-----------------------------

In todd lipcon testing, this parameter set to 2 seems to increase rate at which we take on writes considerably (duh!) and until he hit HBASE-751, all seemed to be running smoothly.

> Test changing hbase.hregion.memcache.block.multiplier to 2
> ----------------------------------------------------------
>
>                 Key: HBASE-779
>                 URL: https://issues.apache.org/jira/browse/HBASE-779
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Priority: Blocker
>             Fix For: 0.2.0
>
>
> Currently its set to 1.  Under load, seeing fill-cache/pause-while-cache-is-flushed cycle.    Changing multiplier to 2 could make hbase take on load faster (Was set to 1 because compactions used to overwhelm the system but now HBASE-745 added a not-so-dumb compaction algorithim, we might be able to run w/ a value of 2).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.