DrupalCon London 2011 - performance

The Economist: An Informal Technical Case Study

dianadupuis — Sun, 15 May 2011 19:23:46 +0000

For people interested in big websites and their unique challenges, this panel offers a behind the scenes look at The Economist site. A team of experienced Economist developers will talk about the complicated challenges, the innovative solutions, and the still-to-be-solved issues of this popular website. There will also be a (lively, no doubt) Q&A.

Intended Audience:

Developers and business people interested in the technical aspect of The Economist website and the big-website solutions the team has developed.

Questions answered by this session:

How does The Economist handle workflow and quality control?

How does The Economist handle testing?

What performance solutions has The Economist developed?

What aspects of The Economist site are custom-coded in innovative ways?

What's the status on The Economist migration to Drupal?

Schedule info

Time slot:

25 August 14:45 - 15:45

Room:

Fairfield Room

The Path to a Mobile Drupal: Techniques, Tools and Failure

JohnAlbin — Thu, 21 Apr 2011 13:39:45 +0000

John Albin Wilkins

Recently, I received an email invite for a webinar on mobile device development. I tried to sign up via my iphone, but was told that my mobile device wasn’t supported. True story.

Intended Audience:

Front-end developers, designers, site builders and even decision makers will find this session essential in understanding the Drupal mobile landscape.

Questions answered by this session:

What does “mobile context” mean?

What are the performance implications of mobile devices?

Which mobile technique is better?

What Drupal modules will help you build websites for mobile?

How does Drupal’s low cost of failure help all of us?

Schedule info

Time slot:

23 August 10:45 - 11:45

Room:

Concert Hall

Damn Quick Drupal: How to Make Drupal Perform and Scale Like a Rockstar!

soyarma — Fri, 15 Apr 2011 12:44:01 +0000

Michael Cooper

I've often heard folks complain that Drupal doesn't scale well and has issues with performance. You'll hear people saying it isn't suited for large sites, or that it is bloated and too slow. A year ago, after a Drupal site failed abysmally under load (in less than 60 seconds) I was wondering if all of those statements and predictions were true.

Intended Audience:

Coders and system administrators who want to make their Drupal site perform like it is just running core. How to make busy sites run really well on even a single server.

Questions answered by this session:

How do I run a busy site with fast page load times

What is the difference between things like APC, memcache, memcached, authcache, boost, etc?

What exactly will pressflow do for my site--both for authenticated and anonymous users

How can I find out what I need to cache most

What are the trade-offs and caveats

Schedule info

Time slot:

24 August 12:30 - 13:30

Room:

Concert Hall

Slides:

DC London Presentation.pdf