Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E861EE55D for ; Sun, 17 Mar 2013 16:48:29 +0000 (UTC) Received: (qmail 35114 invoked by uid 500); 17 Mar 2013 16:48:29 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 34936 invoked by uid 500); 17 Mar 2013 16:48:29 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 34924 invoked by uid 99); 17 Mar 2013 16:48:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Mar 2013 16:48:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.210.45] (HELO mail-da0-f45.google.com) (209.85.210.45) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Mar 2013 16:48:23 +0000 Received: by mail-da0-f45.google.com with SMTP id v40so873759dad.4 for ; Sun, 17 Mar 2013 09:48:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:content-transfer-encoding :x-gm-message-state; bh=BjyhxNxmbu11e13z+z38V+8rkVKZbQt0YKMELAF2H+I=; b=MiLLhMCqeLs7C3PD8R4fW4ZRt9sbcu4fmloZq2a1KRAKIkbQwqaxXMq7ZitEuXmBpq 0IWhdget+TM68zynIaK/d1VpMcn3V3yqWRFxI1djTHuud77hl7pdSCJrAzSYtzCfJ949 K8gHvvYpwSMqJLhb3u+JCP26T8Y8xaqYuys4uZpzvZadIxuAHiKcXDaUMpz3VcYZVrAM 4ZxQ/8o35ub94P1Yc6QqSDT2LIvVxe0JsnTdXBovfM4u5RN1Qmgi983asCllXc9vl6HY 7ntREqK8U+z0rW2y/+ezYoe8NxHaqAIHZxzvao5gucQSzFc0E3esa+1CSMUV5ROy9oDI jMLQ== X-Received: by 10.66.219.1 with SMTP id pk1mr6082322pac.120.1363538882515; Sun, 17 Mar 2013 09:48:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.3.197 with HTTP; Sun, 17 Mar 2013 09:47:42 -0700 (PDT) In-Reply-To: References: <1363490631.4437.YahooMailNeo@web140606.mail.bf1.yahoo.com> From: Jean-Marc Spaggiari Date: Sun, 17 Mar 2013 12:47:42 -0400 Message-ID: Subject: Re: Performances Tests To: dev@hbase.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQnJ95JABWNKFwguNtkt4gYxfT5Jd89KEK4pRO2fD+mguJ7k0zxC8huZHGO2Tdbu4ECJup1r X-Virus-Checked: Checked by ClamAV on apache.org @Lars: here is an example of what I use for i in {1..10}; do echo; echo -n $i ; rm -rf /tmp/*; bin/start-hbase.sh; sleep 60; bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation sequentialWrite 1; bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation --rows=3D100 filterScan 1; bin/stop-hbase.sh; done &>> output.txt Giving only 1 as the readers allow to not launch the test as a MR. I have not try the same tests with a bigger number, but I can. @Andy: LoadTestTool is also on my list, but for YCSB it's a but harder since I will need more than one dedicated computer. But I will look at it too. I might be able to remove 1 node from my cluster and dedicate it to the tests when required... I will be pretty buzy next week, but before next week-end I will try to prepare the LoadTestTool scripts to run something similar. With multiple scenarios, like with and whithout bloom, etc. If yu have any recommandation/request, feel free! I will come back soon with some additionnal numbers. JM 2013/3/17 Andrew Purtell : > I'm not sure I trust the results of PerformanceEvauation. > > LoadTestTool and YCSB have their own issues but seem to produce more > consistent results. I've been thinking on adding scanning and filtering > tests to LoadTestTool. > > On Sunday, March 17, 2013, lars hofhansl wrote: > >> Cool. The 0.94.3 scanning improvements seems almost unbelievable >> (especially since many of my improvements to reduce the internal frictio= n >> went into 0.94.4). >> I would like to track down the random read regression. >> >> Can you send the commands you ran? Are you running this as M/R job or >> standalone client? >> >> Thanks for doing this J-M. >> >> >> -- Lars >> >> >> >> ________________________________ >> From: Jean-Marc Spaggiari > >> To: dev@hbase.apache.org >> Sent: Saturday, March 16, 2013 7:03 PM >> Subject: Re: Performances Tests >> >> Hi Enis, >> >> "interesting" in the positive way ;) >> >> Results are there: >> >> http://www.spaggiari.org/media/blogs/hbase/pictures/performances-1.pdf?m= time=3D1363484477 >> >> The improvment on scan are impressive. sequentialRead and randomScan wen= t >> down. >> >> In ran the 0.94.6 tests with RC2. If we have a RC3 I will rerun them. >> >> I will add HFilePerformanceEvaluation soon but I'm facinf some issues >> with it on previous HBase version... >> >> JM >> >> 2013/3/12 Enis S=C3=B6ztutar : >> >> I just finished to run all the PerformanceEvaluation tests on a >> > dedicated computer with all 0.9x.x HBase versions, and I found results >> > interesting. >> > Can you please provide your numbers if you can. What is interesting fr= om >> > your findings? >> > >> > Enis >> > >> > >> > >> > On Tue, Mar 12, 2013 at 5:41 PM, Jean-Marc Spaggiari < >> > jean-marc@spaggiari.org> wrote: >> > >> >> If you run only 1 client with PerformanceEvaluation, it's not running >> >> it over MapReduce, so you don't have this overhead. But you can still >> >> run it if you want to have something more distributed. Might be usefu= l >> >> to have the 2 options. But at the end, LoadTestTool or >> >> PerformanceEvaluation, any of the 2 is good as long as we are adding >> >> those tests. >> >> >> >> I just finished to run all the PerformanceEvaluation tests on a >> >> dedicated computer with all 0.9x.x HBase versions, and I found result= s >> >> interesting. That gives us a good baseline to see if new HBase >> >> improvements are really improving performances. >> >> >> >> JM >> >> >> >> 2013/3/8 Andrew Purtell : >> >> > Tangentally: I think I prefer LoadTestTool over >> PerformanceEvaluation, it >> >> > doesn't depend on nor is influenced by MapReduce job startup. >> >> > >> >> > >> >> > On Fri, Mar 8, 2013 at 10:05 PM, ramkrishna vasudevan < >> >> > ramkrishna.s.vasudevan@gmail.com> wrote: >> >> > >> >> >> @JM >> >> >> I agree with you. Mainly the perf improvement changes needs some >> >> >> testcases. >> >> >> But sometimes the scenario on which the perf improvments happens a= re >> bit >> >> >> difficult to generate and we will be able to do in a standalone ca= se >> >> only. >> >> >> May be overall if we need to get that perf improvment result we >> need a >> >> >> real cluster with suitable data. That is what i have experienced. >> Just >> >> >> telling. >> >> >> >> >> >> Regards >> >> >> Ram >> >> >> >> >> >> On Fri, Mar 8, 2013 at 7:28 PM, Jean-Marc Spaggiari < >> >> >> jean-marc@spaggiari.org >> >> >> > wrote: >> >> >> >> >> >> > Hi, >> >> >> > >> >> >> > In HBase we already have PerformanceEvaluation which gives us a >> good >> >> >> > way to validate that nothing broke HBase speed in the recent >> updates. >> >> >> > >> >> >> > I can see in the JIRAs many improvements coming, like for the la= zy >> >> >> > seeks, the bloom filters, etc. however, there is no tests for th= ose >> >> >> > improvements. >> >> >> > >> >> >> > Will it not be good to ask people to add some new tests in >> >> >> > PerformanceEvaluation when they are introducing an improvement >> which >> >> >> > is not covered there? >> >> >> > >> >> >> > We should not touch existing tests because we need to have a way= to >> >> >> > compare the baseline between the different versions, but we can >> still >> >> >> > add some new. Like in addition to RandomSeekScanTest we can add >> >> >> > RandomSeekScanBloomEnabledTest and so on. And even better if we = can >> >> >> > back port those new tests to previous version. >> >> >> > >> >> >> > The s > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White)