Mod_cache caches final html output - essentially making it a static page for X number of seconds. This is not a good idea if you have ever changing data displayed/different variable input. As Michael said, it seems the Drupal boost does a similar thing, but at application level (so it may be slower)
A PHP Cache/Accelerator compiles and stores the PHP source for later retrieval. Having pre-compiled PHP eliminates the JIT compilation - therefore speeding up page display. Pre-compiled PHP still allows dynamic variables etc, so you can still view dynamic pages, just after. Such accelerators are: Zend Optimiser, eAccelerator, MemCache etc Each has their merits, but both perform different levels of caching. It may pay to research what you are trying to achieve as to what type of cache you require. The company I work for uses Drupal extensively with eAccelerator to speed things up. (between 50%-70% on average). I implemented some mod_cache settings on a few of our sites for testing, but it wasn't suited to our environment - YMMV. ~ C -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Sent: Wednesday, 28 October 2009 3:50 p.m. To: [email protected] Subject: [phpug] Re: [Slightly-OT] Amnesty International harnesses the web for human rights - MEDIA RELEASE 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] -~----------~----~----~----~------~----~------~--~---
