high performance

I work for New Relic. As Dries pointed out last week on his blog, http://buytaert.net/playing-with-new-relic-on-acquia-hosting we now have a Drupal performance management service available. You can use it to see where Drupal is slow... and you can track the problem down using real production data. We are currently looking for people willing to try out our latest agent in High Performance Drupal environments. check us out http://newrelic.com/php-app-performance.html - we want feedback from the community about our instrumentation.

This year at the DrupalCon Copenhagen we had a lot of different performance related Sessions. I watched mostly all of them and in the end I need to tell, that they are no big differences between them.

Now the Session Proposal for DrupalCon Chicago 2011 is open and I thought, why the different speakers can't organize before and make only two or three performance sessions, but them really great!

I'm thinking about a first sessions for beginners in which High Performance for Drupal is first explained, with some easy stuff.

We frequently use GlusterFS ( http://www.gluster.org ) in load balanced clusters to synchronise the /files directory between the web heads. That works great but we haven't found (or investigated fully) a method that the Boost module could be used easily alongside? I'm hoping someone's already doing it and can provide a proven working example.

Boost in this scenario is being used to complement memcache and standard page caching to provide static page delivery for high volumes of anonymous users, open to other equivalent suggestions appropriate to the environment too.

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)

Amazon has announced micro instance, which is cheaper. The sluggish apache2 stack may not work well on this limited resource. So I am planning to install drupal on nginx and sqlite, with custom compited lite php.

Can some of the functionality that is available in Boost and similar modules, be achieved by just using Apache's mod_cache, mod_disk_ache and mod_mem_cache modules?

I'm on the customer development team at Pantheon and We're working hard on improving Pantheon. We have a few new features that we've been working on, but we'd like to know how to budget the rest of our time before Copenhagen.

We're currently looking to talk with people who deal with hosting (either as a client or as a developer). We want to learn what you dislike about your current development server & hosting options, and what you think would make them better. This knowledge will directly influence what features we develop first.

I'm on the customer development team at Pantheon and We're working hard on improving Pantheon. We have a few new features that we've been working on, but we'd like to know how to budget the rest of our time before Copenhagen.

We're currently looking to talk with people who deal with hosting (either as a client or as a developer). We want to learn what you dislike about your current development server & hosting options, and what you think would make them better. This knowledge will directly influence what features we develop first.

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.

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.