Join GitHub today
Persistence at Restart #370
I really love Memcached, and that's what I've always used so far for all my projects.
However, as my projects have been growing, a restart (e.g. upgrading Memcached, restarting the server, etc...) is always an inconvenience, only because Memcached won't persist the data.
It's not so bad for cached data that can be retrieved from the database, but I store sessions in Memcached, and flush every few minutes to the database, to increase performance (and decrease database load).
However, when Memcached restarts, it causes an inconsistency in the sessions.
Just wondering - is there any way I can make Memcached persist at restarts?
If not, are there plans to implement this in the future?
I see that Redis implements persistence, and a lot of people seem to be preferring Redis over Memcached.
#342 seen this by chance?
In general "cache is a cache" is a good argument, but I recognize this use case.. been clearing bugs and the DDoS fallout but I'll probably get this finished in the next month, maybe?
There're a lot of caveats with it: If you're going to miss invalidations while it's down, you now have cache inconsistency.. if you want to reboot, you'll need to copy the file to disk and back inbetween reboots, etc... but it should all work. The POC worked it's just not complete.