Ok maybe you should try exactly that instead of using zk-latency.py. Create 600 sessions and do a get once every minute. ZooKeeper should be able to handle that.
On Tue, Apr 8, 2014 at 7:05 PM, Check Peck <[email protected]> wrote: > Actual scenario will be - > > > Test :- 3 node ZK cluster, 600 sessions each will do one read > operation(getChildren call) every one minute. > > At what configuration I should try it out. > > > On Tue, Apr 8, 2014 at 6:25 PM, Michi Mutsuzaki <[email protected]> > wrote: >> >> > So my question is what does this line mean at the end? Does it say, it >> > can >> > do a get request call at a rate of 2557 requests per second? >> > >> > get 100 znodes in 39 ms (0.390978 ms/op >> > 2557.689587/sec) >> >> Yes. >> >> > Also I was interested to see how much load a 3 node ZK cluster can >> > handle. >> > In my case, most of the call will be "get" (get the data from only one >> > znode) on the ZK cluster So with the above test I should be able to get >> > some >> > idea right? >> >> How many ZK clients do you expect to have? I would run the same number >> of zk-latency.py instances with higher number of operations to get a >> more accurate picture. The performance also depends on whether you use >> asynchronous reads or synchronous reads. > >
