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 8A6AEEBBE for ; Mon, 21 Jan 2013 20:02:14 +0000 (UTC) Received: (qmail 29792 invoked by uid 500); 21 Jan 2013 20:02:14 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 29745 invoked by uid 500); 21 Jan 2013 20:02:14 -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 29733 invoked by uid 99); 21 Jan 2013 20:02:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2013 20:02:14 +0000 Date: Mon, 21 Jan 2013 20:02:14 +0000 (UTC) From: "Elliott Clark (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-6466) Enable multi-thread for memstore flush MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6466?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1355= 9038#comment-13559038 ]=20 Elliott Clark commented on HBASE-6466: -------------------------------------- Tested this on a small cluster and everything seemed to work pretty well. = Nothing strange happened and there were no pauses. Code in trunk has changed quite a lot since this patch started, so I can't = really pinpoint what was happening.=20 =20 > Enable multi-thread for memstore flush > -------------------------------------- > > Key: HBASE-6466 > URL: https://issues.apache.org/jira/browse/HBASE-6466 > Project: HBase > Issue Type: Improvement > Components: regionserver > Affects Versions: 0.96.0 > Reporter: chunhui shen > Assignee: chunhui shen > Priority: Critical > Fix For: 0.96.0 > > Attachments: HBASE-6466.patch, HBASE-6466v2.patch, HBASE-6466v3.1= .patch, HBASE-6466v3.patch, HBASE-6466-v4.patch, HBASE-6466-v4.patch > > > If the KV is large or Hlog is closed with high-pressure putting, we found= memstore is often above the high water mark and block the putting. > So should we enable multi-thread for Memstore Flush? > Some performance test data for reference, > 1.test environment =EF=BC=9A=20 > random writting=EF=BC=9Bupper memstore limit 5.6GB;lower memstore limit 4= .8GB;400 regions per regionserver=EF=BC=9Brow len=3D50 bytes, value len=3D1= 024 bytes;5 regionserver, 300 ipc handler per regionserver;5 client, 50 thr= ead handler per client for writing > 2.test results: > one cacheFlush handler, tps: 7.8k/s per regionserver, Flush:10.1MB/s per = regionserver, appears many aboveGlobalMemstoreLimit blocking > two cacheFlush handlers, tps: 10.7k/s per regionserver, Flush:12.46MB/s p= er regionserver, > 200 thread handler per client & two cacheFlush handlers, tps:16.1k/s per = regionserver, Flush:18.6MB/s per regionserver -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira