Thesis Cache(r) Beta – 2012-07-31

Through my work at WPEngine I’ve found that using the Thesis Theme can occasionally lead to some performance issues on higher-traffic sites. Nothing spectacular, there are a ton of themes out there that have some issues scaling. Thesis is not special.

But what occurred to me about Thesis, is that it really should be one of the more performant themes out there.  The logic of the theme is organized hierarchically. Thesis passes all html output through thesis_html_framework() which means it is very easy to grab it and cache it, thus adding an additional layer of caching using the WordPress Object Cache.

[download link=”/downloads/”]

Why would you need this if you are already using W3TC or using a hosting company like WPEngine. Both give you various tools for page caching … why use another?

Well, first this plugin is not about replacing your existing caching, but instead making sure that you have adequate caching at the theme level. Even with system level caching there are going to be times where the cache is not served … either because a user is logged in, or because you are getting a lot of traffic and the cache is just missing, or because the cache was purposefully cleared.

ThesisCache(r) just gives you another layer to prevent consuming MySQL/PHP memory if you don’t have too. It gives you page-by-page,post-by-post control over whether to cache a post (or any post type). You can choose to NOT cache a page … or you can even choose to NOT cache the sidebars even though you want to cache the rest.

If you are not currently using ANY object caching no worries, ThesisCache(r) will set up a file-based object cache for you. If you are using an object cache, it will simply leverage what already use.

ThesisCache(r) isn’t in the Plugin Repo yet so here’s the download link. Please report any issues you have in the comments below. I’ll try to deal with them when I can.

[download link=”/downloads/”]

A Wee Bit of Downtime

Sorry folks, we had a wee bit of down last night due t0 my own stupidity but now we’re back up and running. Back to working too much and blogging to little. As most of you know I’ve taken a position at WPEngine and they’re working me like mad, but I’m learning all sorts of new cool crap to bring to my projects so … woo hoo!