caching

Hi,

I would like to share some thoughts about caching in Drupal, and then see what you people think about it. Not sure if this is new though.

Sometimes, cached objects are created on demand (while a page request occurs) and use expiration times. For exemple, cache_filter table usage in check_markup. In these cases, the logic is more or less, like this:

Well, the problem here is that if several page requests come at the same time, there will be several processes doing the same job and caching the same object, concurrently. For hi traffic sites this might be a problem.

Hello

I have set up an aggressive static page caching system using Boost module, which I modified to build gzip compressed pages to speed up load times and be able to serve more pages in less time at cuentosparadormir.com. The system works fine with just a few thousand users in a typical shared hosting account, as the content is oriented mainly to anonymous users. Of course javascript and css files are aggregated and compressed (using smartcache module).

Have anyone tried a similar approach? what do you think the limits of such a set up could be, and what should be the next bottleneck I will face for these kind of sites? do you propose any other configuration to create a high performance drupal site in a shared hosting account?

hi,

i just submitted a simple patch to try to get the ball rolling on memcache support for drupal 6.

has anyone else started on this? is anyone interested on collaborating on updating the memcache module for drupal 6?

cheers
justin

Hi all. I've been working on a new project called Advcache (Advanced Cache) which is a package of caching patches (and a controller module) for Drupal 5. It allows you to cache many things which don't get cached normally, and is intended to increase the performance of Drupal sites, especially for authenticated users. Current caching targets include nodes, comments, taxonomy (trees, terms, vocabularies and node-term bindings), paths, search queries, and forums.

IBM has started a new series of articles that covers OPCODE caching.

Updated

Part 1 - http://www.ibm.com/developerworks/opensource/library/os-php-fastapps1/

Part 2 - http://www.ibm.com/developerworks/opensource/library/os-php-fastapps2/

Part 3 - http://www.ibm.com/developerworks/opensource/library/os-php-fastapps3/

I've just released two modules for developers and maintainers of performance-intensive sites. The first module provides a new, self-tuning, preemptive cache API for modules. It's called PressFlow Preempt. The second module (named PressFlow Preempt Panels) builds on the first by seamlessly offering cached versions of Panels.