WordPress 2.5 Object Cache Improvements

Comments

1. Lazy (3 comments.) says:

   3/20/2008 at 10:34 pm

   It`s a really great article from Neosmart. Peter, he means, that caching makes the site not really dynamic anymore in some cases.

   thanks for the link, i enjoyed reading the article.

   greetings,

   Chris
2. Peter (5 comments.) says:

   3/20/2008 at 11:33 pm

   Thanks for the link – I had no idea that WP could be used with plugins to provide support for memcache to use the memory as the object cache. Should definitely help sites cope with the Digg effect, etc.

   I’m a bit confused by your comment about not having used caching and dynamic content. What do the two have to do with one another?
3. Angels says:

   3/21/2008 at 5:18 am

   Many thanks for the link to Neosmart’s article on cashing.
   As you said it’s really helpful for “understanding the nuances, history and best practices of caching in WordPress”, and that was exactly what I needed to read. Thanks again.
4. Mark Ghosh (386 comments.) says:

   3/21/2008 at 8:05 am

   Peter: Since cached content is not generated for every user, it lacks the personalization that can only be generated by dynamic content. I can only make changes to what I display if the content I am sending to you is generated with the latest information and is not cached from previous visits by others.
5. Mahmoud Al-Qudsi (2 comments.) says:

   3/21/2008 at 8:21 am

   Thanks for the links, Mark.

   I just want to point out that with Object Caching (verses whole-page HTML caching) it is possible to serve personalized content. You just extend each key with the user id, and so each time a call to an object for the same person is made it won’t have to re-create the stuff…

   It’s not exactly the easiest trick in the book, but it can really help if your site is on Slashdot, etc. often; and it’s one of the reasons WP’s object cache is so much better and more flexible than the counterparts (à la Movable Type or the WP Super-Cache).
6. Mark Ghosh (386 comments.) says:

   3/21/2008 at 8:36 am

   Neosmart: I should have mentioned in my comment that it is possible to serve certain types of personalized content even with Object and HTML caching but the code is not for the faint of heart and is not worth the effort in many cases.
7. Carson (46 comments.) says:

   3/21/2008 at 8:59 am

   Forget the advantages and disadvantages of object caching. What I want to know is how Lazy responded to Peter’s question when it was posted an hour later than Lazy’s answer. He might be lazy but he is apparently very intuitive.
8. Mark (386 comments.) says:

   3/21/2008 at 9:49 am

   Carson: There is some oddness in the comments due to the server. We added a timeserver that changed the time in between the posting of the comments. This should be fixed now.
9. Mahmoud Al-Qudsi (2 comments.) says:

   3/21/2008 at 10:02 am

   Mark, if you sort comments in your theme by ID instead of date, that should address the problem.
10. Mark Ghosh (386 comments.) says:

    3/21/2008 at 10:20 am

    Better?
11. Jason (75 comments.) says:

    3/21/2008 at 10:35 am

    This is a pretty good article that outlines some of what I’ve been curious about with WordPress 2.5. I’m looking forward to the final release and a quick 2.5.1 so that I can update my sites and take advantage of some of the newer features and strengths
12. Lazy (3 comments.) says:

    3/23/2008 at 3:40 am

    faster than i used to be.. I`m running on trunk and it really works like a charm now.. with eaccelerator obj. cache (rev 240 (the newest..)) and wp super cache.. got no errors and wordpress 2.5 is really a big deal. i`m looking fordward to 2.6