spymemcached, ketama, and adding new servers

[Dave Peckham]

Hi,

For kicks, I updated that tarball to include a copy of the same test
backed by the Whalin 2.0 client. It worked as expected. I'm just
posting in case this information helps someone else out who might be
exploring the same problem.

http://s3.amazonaws.com/00WYH5EB2EB0ECC08PG2-spyketamatest/spyketamatest.tgz

Dave

Testing with 100000 cache numEntries.
Starting first client with the partial server list.
************* server cur_items **************
localhost:11211 --> 10671
localhost:11212 --> 10732
localhost:11213 --> 10105
localhost:11214 --> 11799
localhost:11215 --> 10256
localhost:11216 --> 11563
localhost:11217 --> 12596
localhost:11218 --> 12198
localhost:11219 --> 10080
******************** end ********************
Got 100000 hits on initial server list.
Shutting down client...
Starting another client with the full server list.
************* server cur_items **************
localhost:11211 --> 10671
localhost:11212 --> 10732
localhost:11213 --> 10105
localhost:11214 --> 11799
localhost:11215 --> 10256
localhost:11216 --> 11563
localhost:11217 --> 12596
localhost:11218 --> 12198
localhost:11219 --> 10080
localhost:11220 --> 0
******************** end ********************
Got 90031 hits after adding the nth server.
Cache disruption % = 0.09968999999999995