• I have several aggregator blogs with a lot of traffic, and quite a few blogposts (3,000 new blogposts per day).

    To optimize the loading of posts, I use Supercache to preload loads of posts (in one go, with no expiration time), and to cache pages/post (with no expiration time). I do not cache the home page nor archive pages so it always shows the correct “last posts”, “archive count” etc…

    Of course, the home page and archive pages load slow. So I am experimenting with DB Cache Reloaded (Fix), to cache ONLY the archive pages and home page (with a 30 minutes expiration time), as a compliment to Supercache.

    All goes well, home/archive pages load much faster, but I still see that DB Cache Reloaded Fix, caches the posts as well. It does not affect the loading of the posts for visitors (once supercache has cached the posts, the HTML is served anyways), but it does load the CPU unnecessarily for the first time each post is cached. At 3,000 blogposts per day, you can really see that the CPU load has increased.

    I wonder what the correct settings are for the DB Cache Reloaded Fix “Cache filter”: I currently have the default “_posts|_postmeta” but I might put more filters in, to only allow the home page and archive pages to be cached.

    The question is: which filters?

    Peter

  • The topic ‘[Plugin: DB Cache Reloaded Fix] Combining DB Cache Reloaded with Supercache’ is closed to new replies.