Updated the read-me with benchmark. Posting summary here:
A 3 Server ensemble running in a single VM, command used(single client)
cluster "127.0.1.1:2181,127.0.1.2:2181,127.0.1.3:2181"-znode_size=100 --znode_count=10000 --timeout=5000 --watch_multiple=5
110000 ops took 16441.6 ms
110000 ops took 16721.2 ms
From my understanding SSL support will have measurable impact in connection setup latency hence CPS bound application will suffer. Due to widespread AES-NI support on CPUs (and Java supports this) I am not quite certain w.r.t latency added for steady state data transfer's encrypt/decrypt process, potentially impacting ZAB. I was hoping that any such measurable latency might show up in smoke tests which were run the past. Let me know if you other perf tests in mind that I can focus on next to get more insight.
I am running into limits of single VM, I would like to run with more clients to replicate past tests