News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Alex Mills' Blog:
Why WordPress Doesn't Have Built-In Persistent Caching
August 13, 2010 @ 11:20:37

Alex Mills has a interesting post to his blog answering a question he and several of the other WordPress developers at Automatic get about their blogging engine - why it doesn't including a default caching layer.

WordPress does actually have a built-in cache called the object cache. It was introduced way back in 2005 1 and it basically caches database query results. [...] However as soon as the page is done being generated, that object cache is discarded. Initially the object cache cached these little chunks of data to the filesystem so that they could be reused on subsequent pageviews. While great in theory, the concept turned out to be terrible in practice.

They opted out of the persistent object caching because, well, it was slower than some of the preexisting alternatives out there like database caching and caching plugins (with WP Super Cache).

0 comments voice your opinion now!
wordpress persistent cache plugin


blog comments powered by Disqus

Similar Posts

Marco Tabini's Blog: WordPress, the GPL and cherries on top

Kevin Schroeder's Blog: Added (PHP 5.3) job queuing to my WordPress instance

JSLabs Blog: How to survive the digg effect

Don Raman's Blog: Call for testing a critical fix in WINCACHE RTW 1.0

Developer.com: Performing HTTP Geocoding with the Google Maps API


Community Events





Don't see your event here?
Let us know!


series list release community install library opinion tips laravel symfony interview introduction package podcast api framework voicesoftheelephpant language deployment bugfix

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework