Hi Michael, Thanks for the heads up.
Boost uses static page caching and works at an .htaccess level, meaning that if a cached file exists Drupal - and hence PHP and MySQL - aren't even invoked. There may be a link here to mod_cache but I'm not certain enough of the details to know. The Boost Drupal module mainly manages production and expiry of cached content and the performance improvement we got for a site whose content doesn't change all that often was "dramatic" to say the least. There are some caveats, which I'd be happy to discuss if anyone is thinking of going this route... :) Paul On Wed, Oct 28, 2009 at 3:49 PM, Michael <[email protected]> wrote: > > On Wed, 28 Oct 2009 15:43:56 Paul Bennett wrote: > > Hi Cam, > > > > It is: > > http://drupal.org/project/boost > > > > :) > > > > Paul > > This capability is built in to Apache with mod_cache enabled. > > There are two options - disk (default) and memory caching. > > For the most part disk caching works well and I am currently testing memory > caching. > > This is preferable imho for anyone deploying any system that doesn't have > the > option already built in to the CMS. > > > > --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
