Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 84254 invoked from network); 18 Feb 2009 10:24:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Feb 2009 10:24:07 -0000 Received: (qmail 40832 invoked by uid 500); 18 Feb 2009 10:24:06 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 40808 invoked by uid 500); 18 Feb 2009 10:24:06 -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 40797 invoked by uid 99); 18 Feb 2009 10:24:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2009 02:24:06 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mirage1987@gmail.com designates 72.14.220.157 as permitted sender) Received: from [72.14.220.157] (HELO fg-out-1718.google.com) (72.14.220.157) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2009 10:23:58 +0000 Received: by fg-out-1718.google.com with SMTP id l26so664721fgb.35 for ; Wed, 18 Feb 2009 02:23:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=a6zHwF0Aj5vQlsK63NJWglNypvyr+aVxyhpmA0aIfl0=; b=fI7GoOlbaF6An6s/PW432AyucgNkVpcRv+Px/35HIahHWJ5IbhPSxlxRXCgAmxss+H jPEL/hUs2M9JAVqOm77cmmigdxXK9C0LzNBkOYfH7SFT0b/RVkN1tS+PAu3bYdkSHMJG A+izwkQckiPqgBwTZ67SDgW1GygNMXz7K+aks= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=DYr4Xm8RVv0pbZdSIczu6FFMsHa5kvr42fguoXqmilLDvLpLjlgqeDmdhyDf0RwRUX +k0qZ1ctxNsPcyayL9EICeVMFbv5JaTXvHsCmgX0arx2ni4D8sQDdzzLklNYKYAwGIhk 1n/73waTZ8RXkuBB8KGwk7ZYVbmRoI6WymXNQ= MIME-Version: 1.0 Received: by 10.86.51.10 with SMTP id y10mr2667541fgy.9.1234952618168; Wed, 18 Feb 2009 02:23:38 -0800 (PST) In-Reply-To: <7c962aed0902172113v7f907f23wa0ae748c442b64c2@mail.gmail.com> References: <534ab810902170901k14d82924scb72ac6519f84b68@mail.gmail.com> <534ab810902170931w56aee8f9h11ac0d46ed7b5ef1@mail.gmail.com> <74f4d40b0902171047lbbae67esb5e028ee90842fa7@mail.gmail.com> <534ab810902171129v6c969148p1743ccd5c647bdf8@mail.gmail.com> <7c962aed0902172113v7f907f23wa0ae748c442b64c2@mail.gmail.com> Date: Wed, 18 Feb 2009 11:23:37 +0100 Message-ID: <534ab810902180223t2fcd949ci8890911b19398556@mail.gmail.com> Subject: Re: Improving hbase read performance From: shourabh rawat To: hbase-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org hey, "> What do you mean by the above when you say read sequentially? Are you > scanning? (Getting a scanner and then nexting through your hbase table?)." well lets say i have 10 keys that are stored in hbase i want to retrive them If I do the reads one by one the time would be summation of 'get' times of each key Could i do the same thing in parallel. so that all the get's cld occur concurrently so i would get total time as the max of the time taken by any of these keys rather than the summ of individual times " > You will have to wait for hbase 0.20.0 or do as Erik suggests and put a > cache in front of hbase. What are you trying to do with hbase? Serve a > website? " ya sort of but i want to check performance withought the use of cache (random reads) ....can i get such performance in the range of 10 ms with hbase > Yeah, the RPC keeps a single connection per remote server but channel is > shared by request and receive. Testing in past, the more remote servers, > the better, but even if a few only, concurrent HTables got better throughput > than one running requests in series (the single connection is not fully > occupied by requests and responses). > so by a single connection u mean all the gets wld be treated sequentially (one by one) by the hbase even wen the requests come in parallel(even wen different htable instances for the same table are employed)....is there any way i can make it parallel..... The hbase master has one port that it specifies and other is the port for the hdfs (hadoop)....what can be done to increase the number of connection as u said....... Thanx for yr help.