Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "ZooKeeper/ServiceLatencyOverview" page has been changed by PatrickHunt. http://wiki.apache.org/hadoop/ZooKeeper/ServiceLatencyOverview?action=diff&rev1=4&rev2=5 -------------------------------------------------- == ZooKeeper service latencies under various loads & configurations == - The intent of this document is to test the performance of various loads on a ZooKeeper service. + The intent of this document is to examine the performance a ZooKeeper service under various loads. This is not an exhaustive test but meant to shed some light on the how much load can be supported for various hardware configurations. In particular I was interested in seeing how non-dedicated servers performed while varying the number of cpus and clients. === Hardware === @@ -10, +10 @@ All systems had 16gig memory available, however unless specifically noted the JVM's -Xmx option was used to limit the size of the JVM heap to 512m. + All systems had 7200RPM SATA drives. + === Operating System === Linux version 2.6.18-53.1.13.el5 compiled using gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) + + === Software === + + * ZooKeeper 3.2.1 + * java version "1.6.0_05" (build 1.6.0_05-b13) + * Java ?HotSpot(TM) Server VM (build 10.0-b19, mixed mode) === ZooKeeper Configuration === The following basic configuration was used on all serving nodes: + {{{ tickTime=2000 initLimit=10 syncLimit=5 dataDir=<data directory> clientPort=2181 + }}} + A dedicated log device was not used, the data directory is store on the same device as the operating system, the ZK snapshots and log4j logs. The standard zkServer.sh script that ships with the release was used to start the service. No modification were made other than to control processor affinity and heap size as noted in this document.
