Persistent Object Cache
November 14, 2005
One of the big recent additions is the Persistent Object Cache. Objects such as pages, categories, options, and users are saved locally to disk so that WP doesn’t have to make a trip to the database. The object cache is completely pluggable, allowing hosts to tailor the cache to their particular usage and needs. Folks on the hackers and testers lists have been shaking out the bugs. The cache is looking pretty stable as of now.
Entry Filed under: WordPress. .
17 Comments Add your own
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed
1.
Matt | November 14, 2005 at 5:30 pm
I heard it no longer causes premature hair loss. Looking forward to seeing it in action.
2.
Mark Jaquith | November 15, 2005 at 12:48 am
Going to have any speed comparisons for us? I wouldn’t mind hair loss if it is caused by excessive speed, rather than stress.
3.
ryan | November 15, 2005 at 2:04 am
I get modest improvements of a few percent in my Apache bench benchmarks. I think the persistent cache will be of most use to WPMU. Regardless, the resulting code cleanups from having a clearly defined cache API and the ability to replace the cache implementation wholesale are worthwhile improvements. I’d like to see backends for memcached and other caching deamons so that we can compare numbers.
4.
Reno | November 15, 2005 at 4:43 pm
If I have the cache enabled there are pages of PHP safe mode permission problems - so a few integration issues to be sorted out.
5.
Nick Momrik | December 1, 2005 at 11:58 am
Is there an easy way to clear this cache? I did an upgrade (to some of the latest SVN) and had to turn off the caching because it is storing the db_version as nothing/blank somewhere, so it’s not matching the version in version.php and then WP doesn’t display anything.
6.
Jeremy | December 1, 2005 at 6:11 pm
Just empty the cache folder, wp-content/cache/ and the cache will recover on its own.
7.
Ozh | December 3, 2005 at 1:16 pm
How do you disable caching ? I was going to ask for an option allowing to disable this feature, for testing purpose.
8.
Rob | December 6, 2005 at 8:28 am
I’ve been hearing of and seeing some problems with mod_rewrite
permalinks and the new object caching code. I haven’t gotten a chance
to look too far into where this might be coming from yet, but its
something to keep your eyes open for.
9.
InteresteDIN | December 7, 2005 at 3:22 am
You’ve said that the object is pluggable, i’m sorry, but where can i find the plugins?
10.
Linda | December 7, 2005 at 8:46 am
Seems like life is gonna be easier (at least for some people :)) )
…. er… hopefully…. in the nearest future. But are you sure that all the OS will be able to make it pluggable?
11.
geek ramblings » Ne&hellip | December 23, 2005 at 10:40 pm
[...] One of the best articles is probably What’s New in WordPress 2.0? over on Owen Winkler’s site. There are also several articles over on Ryan’s site which detail some of the new changes. [...]
12.
{那么骄傲。} »&hellip | December 24, 2005 at 12:56 am
[...] One of the best articles is probably What’s New in WordPress 2.0? over on Owen Winkler’s site. There are also several articles over on Ryan’s site which detail some of the new changes. [...]
13.
lâmpada azul [jcraveiro.&hellip | December 26, 2005 at 4:20 pm
[...] Persistent Object Cache [...]
14.
Bill Bradford | December 27, 2005 at 12:05 am
and it works great with wp-cache too. yay!
15.
nope. not even kidding. &&hellip | January 8, 2006 at 3:54 pm
[...] I could not for the life of my figure out why until I looked at the source code for wpgetsettings() and saw something about caching. Turns out one of WordPress 2.0’s great new features is Persistent Object Caching which means pages and options can be cached on disk, so when they are served up the server doesn’t have to check their value in the database. This is all great if the cache is correctly updated when these options are changed, but for some reason, it wasn’t in this case. [...]
16.
ThinkLemon » Blog A&hellip | January 9, 2006 at 5:56 pm
[...] But finding it slow on and off I decided to see how slow or fast WordPress 2.0 really is. This new incarnation of everyone’s favorite weblog tool supports ‘object caching’. Caching generally is a good thing. The results? Hmmm not good… [...]
17.
Kampoenk ManikMaya »&hellip | January 9, 2006 at 10:05 pm
[...] New features in WordPress 2.0? A lot of people are still asking what the differences are between WordPress version 1.5.2 and version 2.0. I did mention that a lot of the differences are under the surface, and I mentioned the WYSIWYG editor and the new user permissions scheme. Rather than list the changes here, I’ll point you to those who have already written about it. One of the best articles is probably What’s New in WordPress 2.0? over on Owen Winkler’s site. There are also several articles over on Ryan’s site which detail some of the new changes. Christmas Lights One of the things that I only recently discovered myself is the fact that images uploaded to a post become “attachments” which become sub-pages themselves. In other words, each uploaded image becomes a WordPress page, with its own comments. This gives you the basic functionality of a photo gallery without the need for any external software. Click on the image in this post for an example. [...]