In this recent post to his blog Abhinav Singh looks at caching - more specifically looking at four different caching options: WP-Cache, APC, memcache and the query cache.

Ever since I changed my job (from Business Intelligence to Web development) and started working with my present employer, I have had a chance to work on a lot of scalable projects. From making my project to scale from 20 Million PV's to 100 Million PV's to development of an internal tool, the answer to all scalable applications have been caching. [...] Here in this post I would like to pen down my experiences while working with all the caching mechanism. Their pros and cons. What things you need to take care while working with them and every little tit bit which comes to my mind while writing this post.

For each of the four options he describes what kind of caching they're good for, what they can do and a few "gotchas" to keep an eye out for when implementing them in your application.

If you're a WordPress user and are in the process of an upgrade from PHP4 to PHP5, you might be having a few issues. One problem can be cause by the wp-cache component and this recent post from Shantanu Goel.

The issues range from weird page layouts, to some controls not working, to some errors popping up here and there, and probably your blog not even displaying. This occurs because even though WordPress is PHP5 compatible, some of the plugins you are using might not be.

In his case, it was the wp-cache plugin that was causing the problems. Permissions weren't right to allow it to do its job. This resulted in problems rendering content and with the site acting as it normally would. His solution involved disabling and reenabling the plugin after deleting the cache and lock file the plugin uses.

On the Inside Open Source blog today, there's a "quick hit" post from Jason Gilmore for WordPress users out there using the WP-Cache and being frustrated by it's functionality during the development process.

I'm using WordPress to build out a blog for a new endeavor, and couldn't figure out why I had to go through a rather unwieldy refresh process (disabling a template and then enabling it anew) every time I changed it from within the WordPress administration interface.

It was the WP-Caching mechanism that WordPress comes with that was causing the issue, so he tracked down where to disable it for the duration of the development time. (Options -> WP-Cache -> Disable It).

On the Inside Open Source blog today, there's a "quick hit" post from Jason Gilmore for WordPress users out there using the WP-Cache and being frustrated by it's functionality during the development process.

I'm using WordPress to build out a blog for a new endeavor, and couldn't figure out why I had to go through a rather unwieldy refresh process (disabling a template and then enabling it anew) every time I changed it from within the WordPress administration interface.

It was the WP-Caching mechanism that WordPress comes with that was causing the issue, so he tracked down where to disable it for the duration of the development time. (Options -> WP-Cache -> Disable It).

From the JSLabs blog today comes a helpful tip for those running a WordPress blog that might be taking a beating - like from being linked on digg.

This is usually caused by a large amount of traffic that is overloading your database (because each page that is loaded requires a query or multiple queries). A great way to not only improve the speed of your entire blog, but help prevent the above error from occurring is to install a plugin called WP-Cache.

The WP-Cache plugin automatically caches your pages without the need to install any outside methods. The post steps through how to get it installed and how to

From the JSLabs blog today comes a helpful tip for those running a WordPress blog that might be taking a beating - like from being linked on digg.

This is usually caused by a large amount of traffic that is overloading your database (because each page that is loaded requires a query or multiple queries). A great way to not only improve the speed of your entire blog, but help prevent the above error from occurring is to install a plugin called WP-Cache.

The WP-Cache plugin automatically caches your pages without the need to install any outside methods. The post steps through how to get it installed and how to