Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7344BE4A3 for ; Mon, 18 Feb 2013 01:32:55 +0000 (UTC) Received: (qmail 86243 invoked by uid 500); 18 Feb 2013 01:32:53 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 86194 invoked by uid 500); 18 Feb 2013 01:32:53 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 86183 invoked by uid 99); 18 Feb 2013 01:32:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Feb 2013 01:32:53 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prakash.kadel@gmail.com designates 209.85.210.47 as permitted sender) Received: from [209.85.210.47] (HELO mail-da0-f47.google.com) (209.85.210.47) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Feb 2013 01:32:43 +0000 Received: by mail-da0-f47.google.com with SMTP id s35so2220967dak.6 for ; Sun, 17 Feb 2013 17:32:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:references:from:content-type:x-mailer :in-reply-to:message-id:date:to:content-transfer-encoding :mime-version; bh=14hsZ6ExzN99hetQEUyphFsqXrCAcihYxcuoBhXJzVc=; b=Lv0DkhmDo4MOszWCo9aU4btScf2Gi7asawwy3TYqMNbZ3ZDI/W9T3Tl0IxOA/HJgh/ OfFj8utovonQWciPreqA1ELw6VUX2U16QyOcEbjuRVEf6hqSthQayYYwOBgmhImVD37Y 6dUQFNns9OIIwvma2RDlOqgRnJaZfngklovnUEpT0nBlS8EDif24v6GVKFCPWBu29/OE yq88ZT3Ts/rkkWpPt1Il++v08u6R8JSVhcczQJ3ZB8YU+vPxyoLp21IUtAgUtgXTXqrf RYe0jj5gduoYmZuj5XZmy4iFHhH4sKonIIN/TpAaJZZa1E7BC1CP8Y34qijifVzfqxLr C3LA== X-Received: by 10.68.230.193 with SMTP id ta1mr25249366pbc.103.1361151142381; Sun, 17 Feb 2013 17:32:22 -0800 (PST) Received: from [172.30.33.93] ([175.194.106.18]) by mx.google.com with ESMTPS id td10sm12605811pbb.25.2013.02.17.17.32.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Feb 2013 17:32:21 -0800 (PST) Subject: Re: coprocessor enabled put very slow, help please~~~ References: <78023CDA-6661-4BE1-B5FF-3762119E51A2@gmail.com> <7434AC93-B867-4DAC-8A7B-0A5A4CC386CA@gmail.com> <1361149643.73801.YahooMailNeo@web140601.mail.bf1.yahoo.com> <1361150275.19655.YahooMailNeo@web140602.mail.bf1.yahoo.com> From: Prakash Kadel Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (10B144) In-Reply-To: <1361150275.19655.YahooMailNeo@web140602.mail.bf1.yahoo.com> Message-Id: <9C786227-90FE-46BB-B2A3-01FD182181E2@gmail.com> Date: Mon, 18 Feb 2013 10:32:16 +0900 To: "user@hbase.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-Virus-Checked: Checked by ClamAV on apache.org one more question. even if the coprocessors are making insertions to different region, since i u= se "postCheckAndPut" shouldnt there be not much prefomance slow down? thanks Sincerely, Prakash Kadel On Feb 18, 2013, at 10:17 AM, lars hofhansl wrote: > Index maintenance will always be slower. An interesting comparison would b= e to also update your indexes from the M/R and see whether that performs bet= ter. >=20 >=20 >=20 > ________________________________ > From: Prakash Kadel > To: "user@hbase.apache.org" =20 > Sent: Sunday, February 17, 2013 5:13 PM > Subject: Re: coprocessor enabled put very slow, help please~~~ >=20 > thank you lars, > That is my guess too. I am confused, isnt that something that cannot be co= ntrolled. Is this approach of creating some kind of index wrong? >=20 > Sincerely, > Prakash Kadel >=20 > On Feb 18, 2013, at 10:07 AM, lars hofhansl wrote: >=20 >> Presumably the coprocessor issues Puts to another region server in most c= ases, that could explain it being (much) slower. >>=20 >>=20 >>=20 >> ________________________________ >> From: Prakash Kadel >> To: "user@hbase.apache.org" =20 >> Sent: Sunday, February 17, 2013 4:52 PM >> Subject: Re: coprocessor enabled put very slow, help please~~~ >>=20 >> Forgot to mention. I am using 0.92. >>=20 >> Sincerely, >> Prakash >>=20 >> On Feb 18, 2013, at 9:48 AM, Prakash Kadel wrot= e: >>=20 >>> hi, >>> i am trying to insert few million documents to hbase with mapreduce.= To enable quick search of docs i want to have some indexes, so i tried to u= se the coprocessors, but they are slowing down my inserts. Arent the coproce= ssors not supposed to increase the latency?=20 >>> my settings: >>> 3 region servers >>> 60 maps >>> each map inserts to doc table.(checkAndPut) >>> regionobserver coprocessor does a postCheckAndPut and inserts some rows t= o a index table. >>>=20 >>>=20 >>> Sincerely, >>> Prakash