Upgrade to WordPress 2.0 (if you haven’t already), disable WP-Cache, and make sure /wp-content/cache/ has write access. 2.0 comes with caching of the WordPress content only built in. It’s probably a little more server intensive as the point of the WP2 caching is to avoid DB querying rather than page generation, but it’s worth a try for you.
WP2’s caching is specific to certain data and tables, and does not have significant performance impacts. WP-Cache caches entire pages generated, and makes orders of magnitude impact on heavy sites.
-d
Hmm, it sounds like I’m not ready for that then as my site is loading relatively slowly already on its new VPS home.
Thanks, David.
There are folks around with experience tweaking VPS setups. You need to set the memory on SQL processes, max # of processes, etc. — well out of my range of understanding!
WP-Cache can make a SIGNIFICANT impact on a VPS setup, specifically because it makes the site “more static”.
Also using a bytecode compiler/cache if available is another way to speed things up.
Lastly, you can use ‘alternate servers’, like thttpd/lighttpd, for delivering static content (images), or if properly tuned the entire site.
-d
