Hi @pankajjangir,
With 40k+ posts, a few settings can cause serious CPU spikes — here’s what to avoid:
- Don’t use “Purge whole cache on post edit” — this nukes the entire cache on every single save, which is very expensive at scale. Make sure you’re using the smart purge (related URLs only) instead.
- Don’t enable “Start preloader when cache is purged” — the preloader will try to re-crawl pages after every purge, adding a flood of HTTP requests on top of the save event.
- Don’t disable the purge queue — the queue batches purge requests through a background cron job instead of running them synchronously during the post save. Make sure it’s active (it is by default, so just don’t explicitly disable it).
- Don’t enable fallback cache if you don’t need it — the disk-based fallback cache adds extra file I/O on every request, which compounds quickly on a large site.
Hi,
Thank you for sharing those. If you are still experiencing issues with the latest version of the plugin, please share with us the latest configuration on your site. Please make sure to include all options so we can have a full overview.
Thank you!
