WP-Cache

The dangers of having a weblog and podcast that have some traction bit me today. The webserver box was starting to run away earlier today. I logged in and the server load was over 20. I turned the WP-Cache plugin back on. I had tried it before and don’t remember exactly why I turned it off a while ago. It might have had to do with the dynamic referrals list or something like that. I think I might see about only caching the RSS and not anything else. That might be sufficient to keep the box from getting so hammered.

Published by

dave

Dave Slusher is a blogger, podcaster, computer programmer, author, science fiction fan and father. Member of the Podcast Hall of Fame class of 2022.

2 thoughts on “WP-Cache”

  1. I’ve been concerned about that from day one since I have delusions of grandeur like any self-respecting evil genius. My biggest concern is bandwidth, but if I was using 20% of my shared host’s box, I think I’d hear about it.

    You’ll have to look whether the stats package gets called when a cached page is served. If not there’s a way in WP-Cache to make part of the page dynamic that you can probably use to get the stats updated. I was thinking of using that stats package. If I do anything with it and WP-Cache I’ll let you know.

    IIRC, WordPress (1.5.2) already caches the RSS. WP-Cache does the pages. I redirect my RSS to Feedburner, so I don’t generate the RSS very often in any case. I’m not completely happy with the way I’ve got WP-Cache running yet. I hacked in expiration headers, but I only get them on cached pages. I’ll probably look at Staticise Reloaded some more. It may be better suited to my needs. Then there’s WP 2.0 to consider.

  2. Pingback: Thanks WP-Cache!!! « Jayant Kumar Gandhi

Comments are closed.