Mailing-List: contact common-commits-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: core-commits@hadoop.apache.org
Date: Mon, 29 Jun 2009 21:33:09 -0000
Message-ID: <20090629213309.11930.57318@eos.apache.org>
Subject: [Hadoop Wiki] Update of "ZooKeeper/Performance" by BenjaminReed

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The following page has been changed by BenjaminReed:
http://wiki.apache.org/hadoop/ZooKeeper/Performance

------------------------------------------------------------------------------
  ZooKeeper 3.2 Performance
  
- Below is a throughput graph of ZooKeeper release 3.2 running on servers with dual 2Ghz Xeon and two SATA 15K RPM drives. One drive was used as a dedicated ZooKeeper log device. The snapshots went on the OS drive. The The write requests were 1K writes and the reads were 1K reads. The ZooKeeper was configured such that leaders do not allow connections from clients.
+ Below is a throughput graph of ZooKeeper release 3.2 running on servers with dual 2Ghz Xeon and two SATA 15K RPM drives. One drive was used as a dedicated ZooKeeper log device. The snapshots went on the OS drive. The The write requests were 1K writes and the reads were 1K reads. "Servers" indicate the size of the ZooKeeper ensemble, the number of servers that make up the service. Approximately 30 other servers were used to simulate the clients. The ZooKeeper was configured such that leaders do not allow connections from clients.
  
  attachment:results.png