How to Enable the Default WordPress Object Cache
Published Wednesday, December 26, 2007 @ 2:27 pm • 30 Responses
Recently, while attempting to optimize site performance, I found myself experimenting with various caching mechanisms currently available for WordPress. Specifically, I explored each of the following caching options:
- WP-Cache 2 [WordPress plugin]
- WP Super Cache [WordPress plugin]
- WordPress Object Cache [built-in caching mechanism]
While working with the two plugins, WP Cache 2 and Super Cache, I was pleased to discover crystal-clear instructions on each their respective sites. Having access to installation and usage information greatly facilitated the implementation of each of these caching techniques.
On the other hand, finding information about the default WordPress object cache proved virtually impossible. Finally, after locating some decent information, I was able to confirm my initial suspicions and subsequently decided to post a quick article outlining and describing this very straightforward caching method. Although enabling the WordPress cache turns out to be drop-dead easy, it is always good to be sure that you aren’t forgetting a step or otherwise overlooking some important aspect of the process.
How to enable the default WordPress cache in 3 easy steps
Note: This information applies to WordPress versions less than 2.5 only.
Ready? Implementing the default WordPress object cache is remarkably simple:
1) Enable the caching mechanism — open your wp-config.php file and set the value of ENABLE_CACHE to “TRUE”:
define('ENABLE_CACHE', TRUE);
2) Create the cache directory — create a folder called “cache” and place it within the wp-content directory:
/wp-content/cache/
3) Make the cache folder writable — ensure that the folder is writable by setting its permissions to 755 or 777.
Once you have everything setup, surf around your site and check things out by reloading a few different pages. If the WordPress default object cache is working correctly, you will see a newly added slew of temporary cache files along with a newly created index.php file and wp_object_cache.lock file within the cache directory. Thus, if you don’t see any such files in the cache directory after surfing around your site, go back and recheck that you have correctly executed the proper steps. Note: if nothing seems to be happening with your cache — i.e., no cache files are being generated — you may want to try “rebooting the cache” via the following procedure:
- Disable the cache in
wp-config.php - Delete the cache directory completely from your server 1
- Create a new cache directory, set the permissions, and re-enable caching in
wp-config.php
I have also had luck simply deleting the cache directory and letting WordPress recreate it automatically. Remember, if it doesn’t work the first few times, try a few more times before giving up — it does work!
After you have confirmed that the object cache is working, you’re done. From that point on, or until you disable it, the cache should work as intended, saving you bandwidth resources and saving your visitors time. To verify this, navigate to a long-lost post that is buried way back in your archives somewhere — something that is completely off the radar. As you visit, note the page loading time. Now, visit the page again and compare the results. On average, while the native object cache is nowhere near as effective as either plugin method, it does manage to shave off a noticeable amount of loading time for your visitors. Although the WordPress object cache may not work as well as either of the cache plugins currently available, it is an effective caching method that is a breeze to setup and run. And, best of all, the default caching mechanism works perfectly with virtually all WordPress plugins.
1 Note: One final note concerning the WordPress object cache: all of the files may be safely deleted at your discretion — everything is regenerated automagically ;)
About this article
Related articles
- WordPress Error Fix(?): Increase PHP Memory for cache.php
- How to Cache Mint JavaScript
- Improve Site Performance by Increasing PHP Memory for WordPress
- Quickly Disable or Enable All WordPress Plugins via the Database
- WordPress Feedburner HTAccess Redirect for Default (Non-Permalink) Feed URLs
- Embed Flash and Video via the object Tag
- WordPress Discussion Management: Enable or Disable Comments and Pingbacks via SQL
Dialogue
30 Responses Jump to comment form
December 27, 2007 at 3:10 am
The point that you mentioned, “saving you bandwidth”, I am quite sure that it might still be the same. But I am definitely sure that the Web Server CPU usage will drop down dramatically.
December 27, 2007 at 9:07 am
Indeed, it won’t save any bandwidth.
A noteworthy aspect of caching (be it WP-Cache, the built-in cache or whatever): whenever your blog takes ages to load and you have no clue where the problem comes from, just delete the /cache folder. More often than you’d think, it will fix everything.
On Dreamhost, I simply deactivated the cache on all the blogs I run because it was locking too often (I think the efficiency of it depends on some NFS configuration)
December 30, 2007 at 9:22 am
;-), Anytime Bro Anytime
January 7, 2008 at 2:37 am
More Options for WP-Cache:
define('ENABLE_CACHE', true); // Cache on
define('CACHE_EXPIRATION_TIME', 604800); // Cachetime in seconds
and a small Plugin for control the cache:
http://bueltge.de/wordpress-cache-kontrollieren/479/
You can clear the cache with one click.
With best regards
Frank
January 8, 2008 at 11:50 pm
Welcome!
I have update this plugin with small addon. The plugin clear the cache, when you puplish, edit or delete comment and when you cjange private to puplish. You must not click, this functions is automaticly.
With best regards and sorry for my bad english.
Frank
October 15, 2008 at 12:37 pm
For me this never worked.
I tried deleting the cache folder, enable disable the things a few times but I could never see any files being generated in the cache folder.
Sorry, but your post sucked for me :(
October 15, 2008 at 1:32 pm
Man it worked when I followed the steps and installed WP-Cache-2. So I am not sure where the problem was. Now I can see the cache files in the cache folder
And kuddos to you man. You are the first one who has found that out from over a thousand visitors to my site.
So now probably its time to release this hack where people can put the same on their sites :) Nothing that I am a looser, I created this as a hack. Though to release this for everyone, but then help myself back till someone picks me up on this ;)
Kuddos dude ;)
December 9, 2008 at 12:31 am
There is something wrong wordpress2.7
December 14, 2008 at 9:44 am
Thanks for this bit of illumination on a dark topic. It still seems a bit mysterious to me what the object cache does since the removal of file-based caching. Are cached objects no longer persistent across requests? And why are there still freshly dated files the cache directory of my WP 2.7 installation?
Look at the code I would guess the answer to the first question is no, but the second question makes me think I’m missing something.
As a plugin author, I’d like to be able to cache things persistantly without depending on other plugins, but it’s not clear that the object cache provides this ability.
December 14, 2008 at 10:55 am
WordPress bigger 2.6 has not a cache-directory, WP has now a object-cache.
December 23, 2008 at 12:12 pm
Jeff, I too tried several attempts but no success yet on this one.
Do I need to have Wp-Cache2 and Wp-Super-Cache plugins installed to enable this built-in feature?
Thanks, JK
January 3, 2009 at 7:05 am
Thanks for answering. The files in the cache directory that are puzzling me must be created by something else. They are named with a hash ending in .spc.
February 11, 2009 at 6:27 pm
Maybe you should add a warning at the top of this article, that one can no longer (do the title of this article) “Enable the Default WordPress Object Cache”, (which is apparently the case, if one reads through the comments.) And mention if there is any built in alternatives, or must one resort to plugins? Thanks.
May 11, 2009 at 5:10 pm
On an academic interest resurrected the file based object cache for wordpress. http://www.php-trivandrum.org/wordpress-plugins/wordpress-object-caching-in-file-system.html
July 6, 2009 at 5:04 am
I’m working on a PHP Object Cache. An implementation for wordpress is coming along:
Trackbacks / Pingbacks
- 38 ways to optimize and speed up your WordPress blog | WordPressGarage.com
- HM2K.com » 10 wordpress performance optimisation tips
- Enlaces en mi del.icio.us, 4 12 2008 | Vectoralia
- Fondos de Pantalla » Blog Archive » Enlaces en mi del.icio.us, 4 12 2008
- PHP Trivandrum » Wordpress object caching in file system
- know-how.com.es » Convertir on-line páginas web en documentos pdf
Share your thoughts..
← Previous post • Next post →
« December 22nd, 2007 • Are Adblock-Plus Visitors Seeing Your Content? »
1 • Rasheed
December 26, 2007 at 9:31 pm
Thank you for this post.
But what about chmod 777 ?
Is it safe ?
Thanks