Does Benecaster cache my subscribers’ podcast feeds?

Yes. Benecaster caches feed content by tier, not by subscriber. All subscribers at the same tier see identical episode content, so only one cached document per tier per show is needed — not one per subscriber. A show with 2,000 subscribers across 3 tiers stores 3 cached feeds, not 2,000. This saves the space and work needed from your server.

The cache is automatically refreshed when you publish or update an episode, when an episode’s scheduled release date arrives, when you change your show’s metadata, or when you manually clear it in Benecaster → Settings → Advanced → Clear Feed Cache.

With Redis or Memcached, cache reads happen in memory. Without an object cache, reads come from the database — still fast, but a bit more load on your server for each request.