Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
- 3 machines (dual-core Xeon 3060)
- Hooked up to a gigabit switch
- Each running ZooKeeper 3.3.0
- Additionally, one runs a Java client that will connect to the ZooKeeper on localhost and do n reads or writes of a single object of a given length
- ZooKeeper takes about 20-25% of one core
- The benchmark client uses about 10% of the other
- The kernel uses about 20-25% of each core
- The userspace programs spend most of their time waiting on a futex.
- The replicas are idle.
- ZooKeeper takes about 50% of the CPU
- The kernel uses about 7% of the CPU
- The first replica uses about 60-80% of its CPU on ZooKeeper and about 12% on the kernel
- The second replica uses about 40-60% of its CPU on ZooKeeper and about 12% on the kernel