You could have a secondary memcache pool that you warm up during maintenance periods, then switch over temporarily (using a load balancer).
On Sep 9, 2008, at 6:04 PM, PlumbersStock.com 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.
