[development] Refresh rather than re-create D6 cache

Tomáš Fülöpp (vacilando.org) tomi at vacilando.org
Mon Oct 18 15:47:18 UTC 2010

Earl, that sounds interesting - but are you sure Pressflow does that
currently; all I've located so far is this ancient module (by David Strauss)
http://drupal.org/project/pressflow_preempt that mentions such functionality
("Based on the performance data Preempt collects, it may choose to rebuild
cached items during cron operations.").
I'm looking further, of course, but if you have an URL for more info on that
I'd much appreciate it.

On Mon, Oct 18, 2010 at 17:04, Earl Miles <merlin at logrus.com> wrote:

> On 10/18/2010 3:22 AM, Tomáš Fülöpp (vacilando.org) wrote:
> > Hi,
> >
> > 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.
> >
> > 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 /refreshed/ 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.
> >
> > 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.
> >
> > 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.
> This is the Pressflow caching model. When David Strauss first got into
> Drupal, he did a lot of work with this kind of thing, where caching
> wasn't done when requested, but on cron.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20101018/d7e1402c/attachment-0001.html 

More information about the development mailing list