Sometimes, when you are creating custom solutions in PHP, you don’t have the luxury of speedup caches in Ecommerce and CMS frameworks. The problem is that people arent always experts in database design, and SQL, so pages with messy queries in them tend to load slowly. This can lose visitors interest, and if its ecommerce related, sales.

The idea is simple. Only query the databases when the content changes. If the same content is going to be fed out all the time, then why would you waste your time re-building that content, every time something hit your page?

It’ll save you money if your page gets hit a lot, and it’ll make people happier when they get your page quicker.

So, we keep a copy of the generated page first time its looked at. Using the full url as a reference, we keep them, and when someone asks for the same page again, we give them the cached copy. It’s much faster to do this.

So, lets get stuck in

Create a file called “cache_header.php” containing this:

Then create a file called “cache_footer.php” containing:

";
// Now the script has run, generate a new cache file
$fp = @fopen($cachefile, 'w');
// save the contents of output buffer to the file
@fwrite($fp, ob_get_contents());
@fclose($fp);
ob_end_flush();
?>

in the same folder, create a folder called ‘cache’ and set it to writable by the php, using an FTP client:

Screenshot of permissions

Finally, implement the cache on your dynamic page:

This effectively creates static html of a dynamic file and saves it to the cache. The cache is used if the same url is requested within a certain timeframe. This means that database intensive popular pages load instantly.

Good eh?

The real problem with this system is that it does not pay any attention to pages that are dynamically different due to logins and sessions.

Don’t randomly implement this on any old php software. this is a bare bones example. In order for this to work in a complex example where individuals with different credentials are likely to see different pages, you’d need to have the system aware of their credentials, and display a fresh version of the page, based on the presence of an individual. This is NOT covered in the example, and it assumes that every user gets the same page.

What I tend to do, is leave the main page uncached, and any elements that are custom to the user and experience uncached.

The included elements i will cache. For example, my popular products block, i will cache. When they are pulled into the page by the server, the server merely includes a file, instead of drawing from a database.

Overall this hybrid approach isnt as speedy as caching the entire page, but its very close and as a performance versus benefit tradeoff, it works very well indeed.