Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 96715 invoked from network); 17 Dec 2009 01:20:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Dec 2009 01:20:23 -0000 Received: (qmail 4624 invoked by uid 500); 17 Dec 2009 01:20:22 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 4543 invoked by uid 500); 17 Dec 2009 01:20:22 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 4533 invoked by uid 99); 17 Dec 2009 01:20:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 01:20:21 +0000 X-ASF-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 74.125.92.26 as permitted sender) Received: from [74.125.92.26] (HELO qw-out-2122.google.com) (74.125.92.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 01:20:19 +0000 Received: by qw-out-2122.google.com with SMTP id 3so300179qwe.35 for ; Wed, 16 Dec 2009 17:19:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=tX1IODS1UP4H8QUfFXVQBD6uqmUxBIJamlLuAcgunag=; b=G4KCJnz54PcdCCBl81OTPDrCFTXX81MAHkTjpwNsrU4mkQ/IbQWR2rkeRxknRYKd7U LLSJqHAHFHtOcvFgQ69n3y6miWGGVCoG4rTYHpJVglLyosNTEZTfaD6qGWsBOPpW/OB8 cDK5ntc98OxeACN0utfxyby2rhK6KZ7/j1blE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=uOg9GzfPF1sDA7gxHwzZ6EB0mIQ7B25a6iSrcrOWipW+VcvBvEd1ddD1Xez8FgE9b9 GbILW2YFME3SLTfY8L2xiVsTFVDy7Bemi+2QMUGuGFzADOBYlR4dJ/V1SMP1/IH2jrO0 65rY+5GIG/spUNy6uF8gLl5I8KhEpECVyoqcQ= MIME-Version: 1.0 Sender: saint.ack@gmail.com Received: by 10.229.92.203 with SMTP id s11mr1067889qcm.19.1261012798782; Wed, 16 Dec 2009 17:19:58 -0800 (PST) In-Reply-To: References: Date: Wed, 16 Dec 2009 17:19:58 -0800 X-Google-Sender-Auth: 002d87e2dc7e549a Message-ID: <7c962aed0912161719j6560dac3v5ff5758c1427b51e@mail.gmail.com> Subject: Re: Insert, update performance From: stack To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd6e7a6edbc0f047ae26b45 --000e0cd6e7a6edbc0f047ae26b45 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Dec 16, 2009 at 7:52 AM, Adam Silberstein w= rote: > I was expecting performance to be similar, but I=B9m having problems with > Case > B. In particular, after running continuously for 5-10, the latencies go > way > up and my throughput goes way down to a couple of operations a second. I > left it like this for a while in case there were compactions going on, bu= t > it never returned to its original throughput. I have no problems with Ca= se > A. > So, if you look in the logs on the regionservers, do you see anything? In particular, there is a writes barrier that we'll bring down if we are not flushing fast enough. The default is pretty conservative so the barrier comes down pretty quick. The read load might be slowing the flushing? Or are splits happening at this time? Are number of regions climbing durin= g test B? If you want, post a few regionserver logs somewhere we can pull it and we'l= l take a look at it for you. > Any ideas on what=B9s going on here? It may be related to the concurrent > read > workload, since I successfully loaded 120 million records originally, and > that took several hours. "serveral hours" is good or bad by your estimation? Should it be faster? Thanks, St.Ack --000e0cd6e7a6edbc0f047ae26b45--