Comment #6 on issue 370 by [email protected]: memcached(v1.4.15) dead loop
bug.
http://code.google.com/p/memcached/issues/detail?id=370
Also, presizing the hash table is probably a good idea if you haven't
started doing that already. If you have a big cluster with known numbers of
items, adding it to the startup scripts can shave save some latency from a
fresh start.
It'd also be a perfectly good workaround to test if you believe the hash
expansion code is problematic.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
