posterd

Because WordPress is generating much hidden queries to wp_options tables. So caching only this tables will give you effect. And wp_posts tables generate much different queries, so the caching is not so necessary for them

Please wait till the evening – it will be new version of plugin – 0.6

it uses serialize/unserialize and fwrite/fread to operate with cache.

i wrote this plugin special for one of my sites with much widgets that needed always actual information to be displayed. so with this plugin i’ve got 160 -> 2 queries and 4 second -> 0.5 seconds.

at the moment i’m checking work of plugin with different plugins. possibly increasing of genereation time is because of not supporting one of plugins. so solving problems. hope that it will be fine on every instalation of wordpress soon

Hi, I’ve already made cleaning cache on publish and commenting. It will be awailable in version 0.5, tomorrow in the morning.

Thanks for request. It will be done in next releases (a few days)..

So this problem is solved updating to version 0.3

Please tell me these information:
– Is plugin enabled?
– Does folder /wp-content/tmp and file /wp-content/db.php exists
– Does folder /wp-content/tmp consists of files like 03c7e2b17d923b006fc2ae480b122782
– Do you use another caching plugins (they can output old information on page)

Thanks a lot! I’ve added it to new 0.2 version with link to your site.

If Gzip compression is enabled – it needs to use more CPU.

And I have a proposal for plugin. Is to set max CPU load value for blog (for example 5%). So if the CPU load is higher WPCache gives only cached pages and doesn’t allows to generate new pages (gives some predefined screen “Sorry, the server is gone”).

I had a problem with my hosting too. So wrote a little script that checks CPU load and gives only error screen if needed. So it would be good to give any information available in static.