If you *really* want to do this, there are a couple of people who have created versions that do such a thing.
Or you could switch to Microsoft's Velocity. One problem with reloading data from disk when you restart the data is the question of whether or not the data has changed between the stop and start of the memcache instance? If the data has changed then your cache is bad. Does that make sense? Josef On Tue, Sep 9, 2008 at 9:04 PM, PlumbersStock.com < [EMAIL PROTECTED]> wrote: > > Is there any technical reason that memcache shouldn't dump it's db to > disk when shutdown and restore it when started again? If save/restore > were options I could rewrite my start/stop scripts to do it - those > who didn't want it wouldn't have to have it. > > This would be a handy option for me as it takes me hours to rebuild > after a system shutdown. My backend system is proprietary and slow > which is the main reason for caching everything in memcached in the > first place. I was caching everything in a MySQL db before but > memcached is quite a bit faster and less intensive on my server. > -- "If you see a whole thing - it seems that it's always beautiful. Planets, lives... But up close a world's all dirt and rocks. And day to day, life's a hard job, you get tired, you lose the pattern." Ursula K. Le Guin
