Jacob Santos‘ FuncDoc notes:
The WordPress Object Cache changed in WordPress 2.5 and removed a lot of file support from the code. This means that the Object Cache in WordPress 2.5 is completely dependent on memory and will not be saved to disk for retrieval later. The constant WP_CACHE also changed its meaning.
I’ve just started using the object cache and I’m happy with how it works now, so these changes are somewhat concerning. On the other hand, I’m confident that I’ll see even more performance gains once I get my head around the new cache and figure out how to implement it.
Extra: Peter Westwood’s Cache Inspect looks useful.
Posted February 7, 2008 by Casey Bisson
Categories: Dispatches, Technology. Tags: cache, changes, object cache, performance, wordpress, WordPress 2.5, wp-cache.
5 Comments
Comments RSS
TrackBack Identifier URI
Leave a comment
User contributed tags for this post:
fkhj tk (130) - wordpress 2.5 cache (54) - wordpress 2 5 cache (32) - 89 com (28) - s;s fkhj (23) - www.3 pic.com (23) - object porno (19) - wordpress object cache (19) - w,v fkhj (15) - wordpress 2 5 performance (12) - sex fkhj (11) - wordpress 2.5 caching (10) - wordpress (9) - fkhj (8) - wp-cache wordpress 2 5 (8) - www.3.pic.com (7) - wordpress 2 5 wp-cache (7) - Enable the WordPress Object Cache (7) - wp-cache 2 5 (6) - wp-cache 2.5 (6) - wordpress 2 5 (5) - wordpress 2.6 object cache (5) - wordpress cache 2.5 (5) - Wordpress 2 5 Caching (5) - www.3pic.com (5) - WP Object Cache (5) - 3 pic.com (5) - wordpress 2 5 enable cache (5) - wordpress post object (4) - sexfkhj (4) - cache wordpress 2.5 (4) - fkhj s;s (4) - wordpress feed cache (4) - wp-cache wordpress 2.5.1 (4) - fkhj sex (4) - wordpress bookmark object (4) - wordpress cache removed 2.5 (4) - fkhj tk s;s (4) - www.89.com.my (4) - caching wordpress 2.5 (3) - 3.PİÇ.COM (3) - wordpress 2.5 object cache (3) - enable cache wordpress (3) - wordpress cache url (3) - how to disable wp-cache in wordpress 2.5.1 (3) - sql query cache wordpress 2.6 (3) - wordpress disk caching (3) - w,v s;s fkhj (3) - wordpress rss feed cache (3) - disable cache in wordpress (3) - wordpress 2.5 disk cache (3) - turn off caching in wordpress (3) - s;s fkhj tk (3) - wordpress 2.5 performance (3) - wordpress 2.5.1 cache (3) - wordpress wp_cache (3) - sms fkhj (3) - wp_cache_get wordpress (2) - wordpress cache enable 2.6 (2) - wordpress caching video (2) - cache wordpress 2 5 (2) - wordpress memory cache (2) - caching for wordpress 2.5 (2) - turn wordpress cache off (2) - sear video filme sexe (2) - turn off wordpress cache (2) - probleme wordpress 2.51 permalink memory (2) - object cache 2 5 wordpress (2) - wordpress 2.5 cache plugin (2) - wordpress Caching dont work (2) - SEX FKHJ TK (2) - using caching in wordpress plugins (2) - wordpress Object not found! (2) - w,v fkhj s;s (2) - where do rss feeds cache wordpress (2) - wordpress 2.5.1 speed (2) - enable cache in wordpress 2.5 (2) - wordpress $post object (2) - wp 2.5 Cache (2) - wp_cache plugin (2) - memory caching wordpress (2) - turning on caching in wordpress (2) - wp_cache_get wordpress 2.5 (2) - turn on object cache (2) - wordpress 2 5 cache disable (2) - www.world sexe pic.com (2) - wordpress cache 2.6 (2) - sms.fkhj. (2) - fkhj\s;s (2) - get post from cache wordpress (2) - cache 89 com (2) - wp object cache 2 5 (2) - WWW 3 PIC COM (2) - porno object (2) - mss (2) - wordpress cache enable (2) - São Paulo (2) - filme sexe (2) - wordpress object cache plugin (2) - changes in wordpress 2 5 (2) - gender 3pic xxl (2) - wordpress cache 2 5 (2) - 2 5 object cache plugin (2) - time passing quote (2) - wp_cache 2 5 (2) - wep finder (2) - Persistent Object Cache wordpress (2) - wordpress 2.6 cache (2) - wordpress disable category cache (1) - fkhj 1 (1) - wordpress disable caching (1) - problems wp-cache wordpress 2.6.2 (1) - wordpress wp-cache 2.5 (1) - Using the WordPress Object Cache (1) - www.arab 3pic.com (1) - speed problem wordpress 2.5.1 (1) - WP Cache Inspect (1) - wordpress object cache plugins (1) - wordpress object-cache problems (1) - wp_cache no meta file (1) - post object wordpress (1) - wp_cache compatible (1) - wordpress 2.5.1 RAM OR memory (1) - enable wordpress cache (1) - fkhj sexe (1) - fkhj vedio (1) - enable caching in wordpress (1) - fkhj tk fkhj tk (1) - wordpress 2.5.1 RAM (1) - worpdress object cache (1) - wp-cache memory disk (1) - objetc tag allow wordpress post (1) - turn off cache on one page wordpress (1) - wordpress cache feed (1) - geo plugin wordpress 2.5.1 (1) - www.3 pic.com sex (1) - sexe xxl.tv (1) - wordpress cache turn off (1) - wordpress 2.5.1 cache plugins (1) - enable wp object cache (1) - image finder wordpress 2.5 plugin flickr (1) - nable wordpress cache (1) - fkhj tk s;x (1) - wordpress enable persistent object cache (1) - enable cache in wordpress (1) - 3pic,xxl (1) - disable cache wordpress 2.5 (1) - wp-cache wp 2.5 (1) - wordpress 2.5.1 changes (1) - wordpress 2.5.1 Object not found! (1) -
Actually, if you use the functions, you will have no problems, a few functions were removed, but all of the functions that plugin authors and core uses are still there and will remain. The only functionality that was removed was the enable cache and disable cache constants, so you can only disable the cache by using the new constant and replacing the current cache.
By using the caching functions you are doing your users a favor, so keep up that good work!
@Jacob Santos: I’ll definitely continue to code for them, but my concern is on the sysadmin side. The disk-based system is easy (if obviously not as efficient as a persistent memory-backed cache). I just need to learn more about that part.
I found some problem in using Object Cache in WordPress 2.5.
I have use the function wp_cache_set to cache the object, then I use the function wp_cache_get to get the object, but it return false.
the cache function in my plugin works in WordPress 2.3, but it doesn’t work on WordPress 2.5
can you help me to have a look my plugin?
my plugin is http://wordpress.org/extend/plugins/top-first-commentors/
thanks in advance
I will say, that it appears that you are setting the top commentors after you call the get cache function. Following the logic, your plugin would preform best with disk caching where it would just pull from that.
I would keep it like that or use another caching plugin. Currently, it appears that you are caching it to memory after you try to get it, which doesn’t help on the next page load when it must still preform the SQL query.
I just finished posting about the changes to the WP object caching system, including a history of WordPress’s caching abilities and memory-based extensions to the WP object cache that are WP 2.5 compatible… Hopefully it’ll provide some further insight into the matter: http://neosmart.net/blog/2008/wordpress-25-and-the-object-cache/