Timwi wrote:
Tim Starling wrote:
Because the client algorithm distributes keys to each available server equally,
Is this a shortcoming of the PHP version of the memcached client? This is certainly not true for the Perl version; you can specify weights there.
Before we fixed it, the PHP client sent every key with a key length longer than about 8 bytes to the first server on the list. Since pretty much all our keys are longer than 8 bytes, this caused some problems. I still haven't sent a patch upstream for that one. I can rant all day about problems with memcached, both in the clients and in the server. As soon as I find (or write) a suitable alternative, I'm switching to it. Perhaps some sort of LRU cache wrapper around TreadMarks or SAM would do the trick.
-- Tim Starling