load

ATTACHED: comparison of download waterfall before and after applying these hacks to my page.

Hi Team,

I wanted to share with you some techniques I've discovered over the last couple of days that seem to have a noticeable impact on download times. These are especially applicable to pages with large CSS files on first load, as once things get cached it doesn't make much difference.

Hi all.

I've been tasked with building a high performance, high capacity website for a client and so have been reading up on best practices. I'm getting familiar with the cache based approach for both authenticated and anon. users, APC, varnish etc - however I'm finding it difficult to find best practices regarding non-cachable requests.

-- EXAMPLE --

Suppose my website were to give away 500 free donuts to the first 500 people who correctly answer a multiple choice question. This figure would be stored in a field called "QTY" on the "freebie" content type.

Hi guys, first time posting here after using these forums for several years with great success. I have been building Drupal sites for a couple years now, and performance has always just been okay for me. The most recent site I am working on seems to be slower to load than most. I am looking for advice on how to make this site load faster. It is not a huge and overly complex site, doesn't seem like it should be this slow.

It is the latest Drupal install, and all up to date modules. There are about 50 modules, if it helps to provide a list of those I can.

Tools like ab or siege are inadequate for testing sites served by Nginx (or Lighttpd). They both use threads instead of multiple processes. ab is based on the Apache Portable Runtime, hence it uses the same type of request handling at the OS level that Apache uses.