isn’t writing cache to disk an overhead when everything is cached on CDN

Hi @cleverschooling,

is it true that when everything is cached on CDN, writing cache on disk becomes unneeded overhead.

– Not true. When CF sends the first request if you don’t have a fallback cache, the WP system will execute your code and generate the HTML and then it gets cached on the CF cdn edge that requested for that content.

Now if a different CDN edge request for that same which, that same process happens again. But when you have fallback cache enabled, the system will generate a disk-level cache for your pages. SO, when the request comes instead of WP executing all the PHP to generate the HTML it will get directly served from the fallback cache, with a much lower TTFB as the server didn’t have to process all the codes.

Again if your cache expires on CF, then again the process will happen. So, not enabling fallback cache means for all these cases the origin server will have to process the request and generate the HTML dynamically.

It is very important to know how CF cache actually works. Read this article: https://acnam.com/untold-truths-of-cloudflare-cdn/ which will give you a clear picture about CF CDN and how it works.

if a different CDN edge request for that same which, that same process happens again

thank you