Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-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 9EC6B109EA for ; Wed, 9 Apr 2014 03:55:32 +0000 (UTC) Received: (qmail 88918 invoked by uid 500); 9 Apr 2014 03:55:26 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 86788 invoked by uid 500); 9 Apr 2014 03:55:21 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 85971 invoked by uid 99); 9 Apr 2014 03:55:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2014 03:55:18 +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 mutsuzaki@gmail.com designates 74.125.82.47 as permitted sender) Received: from [74.125.82.47] (HELO mail-wg0-f47.google.com) (74.125.82.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2014 03:55:14 +0000 Received: by mail-wg0-f47.google.com with SMTP id x12so1853237wgg.18 for ; Tue, 08 Apr 2014 20:54:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Q2SCnKjjn+eQd3yurZYWWA8hFVmYrfeydsOb4R+jNcU=; b=K73he2ohaHUw0Q/chxt2D3rhaTDG9m/kAkaJOh5I83oydSeN8auYQ7kZtn2x561HwR 6MMa8bkKA3Ohlx+e7buhv6PseJfE+1LpVb1n/E7SJEgorDCVcwaObFBbshiStWIO9b5C 6qOy7wyvokdAjlDLOJEMODuMhlivRyNd58Di/XtTaWoIwYr6tF47H1bIscrG2pYea49i sgFgXK9aCeOFt/4NFN0QRkf0QglaDkHvZbZHFQKMkZGniUNs9QAMe6OOKwNtOegfDY7Z ZM5+ZCOEDTS0sQobYYATqUuKdkOWn9Y2+RN/tqfU1wOveju31YXpOEEowbpa+0ljFYR3 3Quw== MIME-Version: 1.0 X-Received: by 10.194.161.168 with SMTP id xt8mr7108177wjb.35.1397015692605; Tue, 08 Apr 2014 20:54:52 -0700 (PDT) Reply-To: michi@cs.stanford.edu Sender: mutsuzaki@gmail.com Received: by 10.194.103.40 with HTTP; Tue, 8 Apr 2014 20:54:52 -0700 (PDT) In-Reply-To: References: Date: Tue, 8 Apr 2014 20:54:52 -0700 X-Google-Sender-Auth: 7iSCQTIHTot07Fa-bJHUWbsE2n0 Message-ID: Subject: Re: Load on Zookeeper cluster? From: Michi Mutsuzaki To: Check Peck Cc: user Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Ok maybe you should try exactly that instead of using zk-latency.py. Create 600 sessions and do a get once every minute. ZooKeeper should be able to handle that. On Tue, Apr 8, 2014 at 7:05 PM, Check Peck wrote: > Actual scenario will be - > > > Test :- 3 node ZK cluster, 600 sessions each will do one read > operation(getChildren call) every one minute. > > At what configuration I should try it out. > > > On Tue, Apr 8, 2014 at 6:25 PM, Michi Mutsuzaki > wrote: >> >> > So my question is what does this line mean at the end? Does it say, it >> > can >> > do a get request call at a rate of 2557 requests per second? >> > >> > get 100 znodes in 39 ms (0.390978 ms/op >> > 2557.689587/sec) >> >> Yes. >> >> > Also I was interested to see how much load a 3 node ZK cluster can >> > handle. >> > In my case, most of the call will be "get" (get the data from only one >> > znode) on the ZK cluster So with the above test I should be able to get >> > some >> > idea right? >> >> How many ZK clients do you expect to have? I would run the same number >> of zk-latency.py instances with higher number of operations to get a >> more accurate picture. The performance also depends on whether you use >> asynchronous reads or synchronous reads. > >