If you're suffering from cache reheating issues that only stem from restarting the process then maybe. If the reheat issues stem from a reboot then you're still

If you're suffering from cache reheating issues that only stem from restarting the process then maybe. If the reheat issues stem from a reboot then you're still screwed. The numbers presented only make sense in the event that your cache hit rate is uniformly distributed. In the event that you have a normal distribution or pareto distribution (more likely for a website) the majority of your cache hits come from very few entries meaning your cache can probably be reheated to 80% with 20% of the data, or 200GB instead of 1 TB. A much better idea that actually solves the problem instead of discussing implementation artifacts (memory mapped files) is to reuse your tracking data (eg. this page gets X number of hits) to pre-heat the caches before the server goes live. All you need to do is build a histogram of your cache hits over the last X minutes and flush it to disk every now and then.