<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">What would be the practical difference between emptying and recreating a cache, and refreshing it?<div><br><div><div>On 18/10/2010, at 9:22 PM, Tomá Fülöpp (<a href="http://vacilando.org">vacilando.org</a>) wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>In D6, after all caches are cleared, or after a lot of them expire and get emptied by cron, the server load spikes seriously because all such caches need to be re-populated.<br><br>Since this happens more and more on sites I work on, I have been thinking about using another approach in my modules, in the sense that caches would be <i>refreshed</i> rather than cleared and re-populated. Each cache refresh would run depending on e.g. a simple variable storing last time stamp of any other cache refresh.<br>
<br>This would assure that a) all cached values would be available at all times, b) caches would never be re-calculated all at the (near) same time.<br><br>I am about to write logic for this, but wanted to first check with others in the list -- perhaps some of you know or can point to an elegant solution that already exists.<br>
<br>Thanks!<br><br>vacilando<br><br><br>
</blockquote></div><br></div></body></html>