cache

Yesterday I was invited to the meeting in office of Gorod.ua, the Ukrainian web portal, to speak about Drupal performance. The way like those guys are using Drupal is good, however there is lack of performance. They are spreading a spirit of their child to the whole of Ukraine, so it is a time to expect more visitors. We spoke a lot and I got better understanding of what is needed. We touched many problems, including not typical and theoretically solved them.

Hello,

I am currently experimenting with different cache strategies and came across the following question:

Is it problematic, ignoring cache fragmentation issues, if I enforce a general TTL on CACHE_PERMANENT items, eg. purging every item x hours after its creation?

Clearly, just purging the whole cache does not create any problems, but are there any known problems when cached items disappear one by one?

Thanks,
martin

Hi all,

My Drupal website is running very slow and we just wake up to trying to optimize the performance. I read a lot of thing about performance and caching system before and my main reason to post here is that I'm a bit confuse so I need some advice to find the best way to increase the perfomance of my site.

Maybe my post will also help high perfomance beginner.

First my website is:
- around 130 modules enabled (50 custom modules + cck, views, ctools, panels + different front end and back en modules)

Duration: 1 hour

Brief description: How do you create a site that can handle millions of page views per day without crumbling under the load? Caching won't solve all your site problems, but it has to be part of your strategy. In this session we'll cover Drupal's internal caching mechanisms, what Memcache can do for you, the types of scenarios that Varnish can cover, and the whys and wherefores of Edge Caching. We'll discuss the differences between building a static site that can handle thousands of page requests per second, and what it means to your performance when you start adding authenticated users and node edits.

I created a wiki for discussion about the future of Drupal Caching. Please read http://groups.drupal.org/node/75823 and let's discuss in here to figure out how to create a Cache API v2 that surpasses our current implementation.

We had a high traffic site that would significantly suffer every time the front page cache was cleared (either with an update or when the minimum cache timeout was reached). So we updated the Drupal cache system (here's our updated cache.inc or a patch to cache.inc for 6.15) to have one request update the page cache when it expired and during that time other requests get the old version.

I'm working on a unique problem right now with the relaunch of a high traffic site (2-5 million page views per day), and want to run an idea by the group. There is a specific singular landing page that will receive a significant amount of traffic from an external source, and each requested page would have a unique query parameter. Ex: /landing-page?uid=438474383487348?foo=bah.

Hello, does anyone here currently use the D6 CacheRouter module on their site? If so, could you help test/refactor this patch (http://drupal.org/node/746610) to the CacheRouter module. The goal of the patch is to add a second layer of cache backup if your primary caching tier was unavailable. i.e you could have the Drupal db cache tables as a backup to memcache or apc, instead of defaulting to a "cache miss" scenario which could really hammer the database.

Anyone here using Cacherouter Memcached backend (which depends on libmemcached) here ? I don't want to discuss PECL memcached itself, let's just say it's stable enough to be considered on par with memcache.
I'm more interested in Cacherouter Memcached engine code, stability, issues, etc.

Hello everyone,
Recently I released 2 new caching modules for Drupal: Advanced Panels Cache, and Namespice. Check them out. Feedback is welcome!