I've read many articles on memcached, but haven't used it myself. It claims to do failover across multiple memcached servers, but I haven't seen it in action myself, and also what it does when the last server becomes unreachable. I don't know how stable it is, and what the requirements (and administrative overhead) of its users are, and also what its failure modes are.
At PM, we have MySQL behave erratically and grind to a halt from time to time, needing a restart. If memcached also exhibits that ("Just Restart It"), that would introduce yet another slowness problem. And such, I'm wary of enthusiastically following what others claim works for them when I haven't played around with it myself. And I'm looking towards its failure modes because we experience failure modes with MySQL.
In reply to Re^6: PerlMonks Caching
by Corion
in thread PerlMonks Caching
by ahmad
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |