Manage your files responsibly

The content of your applicaiton is the purpose of it's existence, you will likely have to handle associated images of varing contexts. The downside to this is that if you end up with a very large number of files on the file system, it can have a substantial negative impact on the performance and stability of your application.

Leverage Amazon S3 to serve Drupal Application files

This is a timeless subject and one I'm pretty passionate about. There are many reasons you might want to offload your file storage from the local file system and onto Amazon S3. I will cover two implementation methods in this post, and some of the reasons why you would want to integrate S3 with your Drupal application. I will never get sick of talking about best practices for building scalable and performant Drupal Applications.

Keep your 404 requests in check

Did you know that a 404 could cripple your website? We'll believe it or not misconfigured or ignored 404s could be killing your websites performance. Let's see how.

First things first, what do 404s look like in Drupal 7 out of the box? If you view the headers of a 404 page you will see the follow:

Cache-Control:no-cache, must-revalidate, post-check=0, pre-check=0

That Special Relationship With variable_set

I find over and over many performance issues come down to this particular function - variable_set(). In all cases it is a module invoking this function, even under minimal load that proceeds to cause a Database stampede, backend 503s and outages. How can this be? let me show you. This is going to get deep quickly so do your best to follow along since this is really important to understand.

Protect your precious forms

Hey we all know its a nightmare to get spammed by these incredibly annoying bots that patrol the internet which flood websites with uber amounts spam. Well, we have solutions for that. If you are working with Drupal then the likely choice is Mollom which is of course free for small sites and blogs, bonus!

Take care of your cache_form table

Little too often I come across a cache_form table that is bursting at the seams, not from anything bizarre, although that actually happens a lot, rather simply because developers lose track of its intended purpose and id like to think they inadvertently abuse it. With a bit of initiative i've witnessed 79GB cache_form tables reduce to 16GB saving their business from the need to upsize disks and threaten stability