Evaluating Memcached for our site. Looking for advice.
rob.sharp at thesoundalliance.net
Mon Oct 22 06:01:47 UTC 2007
On Mon, 2007-10-22 at 13:53 +0800, K J wrote:
> In our case, not really. It really depends on your current
> caching codebase. The only problem is the (current) lack of a
> consistent hashing algorithm  but YMMV.
> What is the consistent hashing part and why is it a bad thing?
The wiki explains the issue pretty well:
"With default clients adding or removing servers will invalidate all of
your cache! Since the list of servers to hash against has changed, most
of your keys will likely hash to different servers. It's like restarting
all of your nodes at the same time."
With a consistent hashing algorithm, node removal will not invalidate
your cache, causing much less of an issue should you need to remove a
node from the server pool.
Hope that helps,
telephone: 02 9282 4038
facsimile: 02 9282 4099
inthemix : FasterLouder : Thought By Them : SameSame
"Poor workers blame their tools. Good workers build better tools. The
best workers get their tools to do the work for them." -- Syndicate Wars
100% recycled electrons were used for the composition of this email
- please don't print it unless you need to!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the memcached