About Fallback Page Cache
-
I use Litespeed web server with lScache plugin and the WP Cloudflare Super Page plugin and this has been working great all together.
But my main problem is that if I enable the fallback page cache option and then disable the cache option in LScache as it is recommended, website works fine but server resources are being used more.
With server resources being used more I mean that –
With LScache enabled and fallback page cache disabled, when tested on loader.io 10k concurrent requests are being handled very easily with low response time and 0 timeouts,
but with the opposite config, I am experiencing timeouts with less than 1000 requests per second.
Although right now I don’t have traffic of that size but do have sporadic traffic bursts, so I was wondering if I have the LScache caching enabled and fallback page cache in this plugin disabled will that cause any problems with the proper functioning of this plugin or should I keep LScache caching disabled and fallback enabled?
I am only using this plugin to ensure that Cloudflare is not caching my wp-admin and caching all other pages.
And also another question,
Don’t the page rules
1. https://website.com/wp-admin/* {cache level – BYPASS}
2. https://website.com/* {cache level – EVERYTHING}serve the sole purpose of this plugin? or there are other features in this plugin which make it worthwhile for me to keep this installed.
Thanks!
- The topic ‘About Fallback Page Cache’ is closed to new replies.