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 === + All systems were : + - All systems were dual quad core Intel(R) Xeon(R) CPUs running at 2.50GHz. Eight cores were available however as noted below Linux's processor affinity feature was used to limit CPU availability to the JVM. + dual quad core Intel(R) Xeon(R) CPUs running at 2.50GHz. Eight cores were available however as noted below Linux's processor affinity feature was used to limit CPU availability to the JVM. 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 === @@ -32, +43 @@ === Test Client === - zk-latencies.py from http://github.com/phunt/zk-smoketest was used as the test client. + * zk-latencies.py from http://github.com/phunt/zk-smoketest was used as the test client. - + * python 2.4.3 == Results ==
