When it comes to web page load time, she should always say “wow, that was fast”.

A Quick update based on Frederick’s comment below

** Please do not take these tips as THE answer, this is a complement, not a replacement. I have purposely not given specifics on how to configure anything, or what value to set, because I don’t want people copy pasting things, and then having their site crashing. Regarding mod_pagespeed, I said it’s the most bang for OUR buck.. it’s not recommended in production, nor do we have it on for everyone else. **.

Webpage load time is getting more and more important these days, if you go into Google Webmaster Tools, you’ll see “Site Performance” under the labs link. This is a very good indicator of what Google thinks how fast your site is compared to the rest …

If you have a wedding photography website, more than likely you want to showcase your work, or the work of your colleagues. You want to do this, without putting up low quality pictures, nor do you want to make your visitors wait 20 seconds before the page loads. Here are two plugins I use for my clients to help with this.

• The Smush.it plugin. This plugin compresses your image using the Smush.it API from Yahoo!, I’ve used it to reduce a page size from 3MB to 1.3MB, which meant that visitors were able to see the site faster, and appreciate the photographs rather than their internet connection.
• W3 Total Cache : This is a fairly advanced plugin that makes your site use MySQL less, and also helps you off load things onto a content delivery network with a few clicks. …

Introduction

A question I recently saw on Stack Overflow titled Faster way to delete matching [database] rows? prompted me to organize my thoughts and observations on the subject and quickly jot them down here.

Here is the brief description of the task: say, you have 2 MySQL tables a and b. The tables contain the same type of data, for example log entries. Now you want to delete all or a subset of the entries in table a that exist in table b.

Solutions Suggested By Others

DELETE FROM a WHERE EXISTS (SELECT b.id FROM b WHERE b.id = a.id);

DELETE a FROM a INNER JOIN b on a.id=b.id;

DELETE FROM a WHERE id IN (SELECT id FROM b)

The Problem With Suggested Solutions

Solutions above are all fine if the tables are quite small and the …

I've just finished reading two recent blog posts about new query optimizations in the upcoming MySQL 6.0, it's all fine and dandy but ...Looking at Correlated semi-join subqueries and PostgreSQL by S. Petrunia we can read something like Quote: The first thing we did was to take a look at PostgreSQL as it is easily available and seems to have at least decent subquery handling (or even better