Interesting. It does seem to suggestion the session expiration is expensive.
There is a concurrent table in guava that provides very good multi-threaded performance. I think that is achieved by using a number of locks and then distributing threads across the locks according to the hash slot being used. But I would have expected any in memory operation to complete very quickly. Is it possible that the locks on the session table are held longer than they should be? 2011/4/18 Fournier, Camille F. [Tech] <camille.fourn...@gs.com> > Is it possible this is related to this report back in February? > > http://mail-archives.apache.org/mod_mbox/zookeeper-user/201102.mbox/%3c6642fc1caf133548aa8fdf497c547f0a23c0c52...@nywexmbx2126.msad.ms.com%3E > > I theorized that the issue might be due to synchronization on the session > table, but never got enough information to finish the investigation. >
