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 BE18210F8D for ; Tue, 29 Apr 2014 00:17:47 +0000 (UTC) Received: (qmail 45620 invoked by uid 500); 29 Apr 2014 00:17:44 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 45436 invoked by uid 500); 29 Apr 2014 00:17:44 -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 45428 invoked by uid 99); 29 Apr 2014 00:17:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Apr 2014 00:17:43 +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 fancyerii@gmail.com designates 209.85.215.53 as permitted sender) Received: from [209.85.215.53] (HELO mail-la0-f53.google.com) (209.85.215.53) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Apr 2014 00:17:40 +0000 Received: by mail-la0-f53.google.com with SMTP id b8so32421lan.12 for ; Mon, 28 Apr 2014 17:17:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=QrBK88z3RM8Xm6TQPT2+iK72iCycQiR/HgFK6NXtUYg=; b=XSEfYn9lXPBaCP1dJdHkIbpKhKK3G6FX+QwIDpSFpkCGaT6hBEzpJSRbX2vQpRhKms nyJpWhg5H/Z4u64oK1z/XqpM56b2ezh2B+OCrD7szqGmnav1elOqKJkjfi7+azvzo4yB VI+rPHI3O8HjYeO2cfJcqf/3HrwH89oXtzLh1N+n9t7CdwMZVdP/2Y7waOVtdMhIaD4G HrG1E5MJhEivshf3Q/74PFrma1w5Pa6tZf5pK8zMUSn7XN5KWXdStDk36fLLZmqML92M N2E5uCOblqaPHxOQ/NGLyrXodCaCjkxf3uKG+iAHZRsgiDydlnDPdDd0dg/niUprXHab 3UxQ== MIME-Version: 1.0 X-Received: by 10.152.19.195 with SMTP id h3mr246617lae.47.1398730637205; Mon, 28 Apr 2014 17:17:17 -0700 (PDT) Received: by 10.112.148.41 with HTTP; Mon, 28 Apr 2014 17:17:17 -0700 (PDT) In-Reply-To: References: Date: Tue, 29 Apr 2014 08:17:17 +0800 Message-ID: Subject: Re: question about threads count From: Li Li To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org but I have many checkAndPut operations. will use batch a better solution? On Mon, Apr 28, 2014 at 8:01 PM, Jean-Marc Spaggiari wrote: > Hi Li Li, > > Yes, threads will impact the performances. If you send all you writes with > a single thread, a single HBase handler will take care of them, etc. HBase > does not provide a single handler for a single client connexion. It's able > to handle multiple threads and clients. > > However, it also all depends on the way you send your writes. If you send a > single puts(<10000>) per seconds, if will not be better to send 10 000 > threads with a single put. > > I will recommend you to run some perf tests on your installation to find a > good number for your configuration. > > JM > > > 2014-04-28 6:27 GMT-04:00 Li Li : > >> hi all, >> with the same read/write data, will threads count affect performance? >> e.g. I have 10,000 write request/second. I don't care the order very >> much. >> how many writer threads should I use to obtain maximum throughput? >>