Persistent Object Cache

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.

17 thoughts on “Persistent Object Cache

  1. 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.

    Like this

  2. 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.

    Like this

  3. 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.

    Like this

  4. 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?

    Like this

Comments are closed.