Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 4943 invoked from network); 25 Feb 2011 23:16:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Feb 2011 23:16:09 -0000 Received: (qmail 7205 invoked by uid 500); 25 Feb 2011 23:16:07 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 7164 invoked by uid 500); 25 Feb 2011 23:16:07 -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 7156 invoked by uid 99); 25 Feb 2011 23:16:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 23:16:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of zslist@gmail.com designates 209.85.160.169 as permitted sender) Received: from [209.85.160.169] (HELO mail-gy0-f169.google.com) (209.85.160.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 23:16:00 +0000 Received: by gyb13 with SMTP id 13so1167656gyb.14 for ; Fri, 25 Feb 2011 15:15:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=FfTPnF2AGQwXJBe5btXmAiMGuyx/bBZ3tj32aQ5puU8=; b=UZBsBTMMV3mNFSmFXRQoLeqb8YwN4FYteLHWG4ZJGFvNb23FPB76dvZzSzcdIObJxo Hwr0L1mYJsAp3LSf8/KKiUlVbQLk5VTnlAB2L6zrTHnEPgZ1BLYo6Qx3g1LNiYQoHooJ VtoWsVcBKjfGHOvq1p/b3W6EmT6v7Wk7uywnk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=plPDR4wO7sdS0H4batUWj3O2PUTygZNNFPqyVpjkSLU5F3/Qi2/+CpbXlT3cJuhCrC L74kETR/TkxXm4UCfynl9VRAnPtu5KnSY3ZC5GyifzV+NzBMNceknnC3s0PYxe0uJNC0 MQJ1/sRbM3OayoUpXc8537XCakDAYR62r3B1U= MIME-Version: 1.0 Received: by 10.150.220.17 with SMTP id s17mr4256016ybg.188.1298675395119; Fri, 25 Feb 2011 15:09:55 -0800 (PST) Received: by 10.150.53.21 with HTTP; Fri, 25 Feb 2011 15:09:54 -0800 (PST) Date: Fri, 25 Feb 2011 15:09:54 -0800 Message-ID: Subject: HTable client help From: benchmark To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=000e0cd4d4fc9af010049d236dcb --000e0cd4d4fc9af010049d236dcb Content-Type: text/plain; charset=ISO-8859-1 We are using 0.20x hbase. We are seeing some big delays on the client's read. The server side stats shows about 2-3 ms, but on the client side we are seeing about 20ms. The network delay is negligible. We have a about 250 threads per JVM each having its own HTable client handle. Reducing the number of client threads to 32 helps a tiny bit, but nothing significant. any ideas? --000e0cd4d4fc9af010049d236dcb--