Question
FastCGI Cache VS WP Super Cache or use Together?
- Posted on October 22, 2018
- CachingNginxUbuntu 16.04
Asked by LS1
I am confused about what I found on web and I want a PRO answer. Why someone would need wp super cache when you can cache dynamic php with FastCGI?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
FastCGI cache is faster than WP Super Cache because the latter uses .htaccess and and PHP itself to route the visitor to the cache (files). So before the visitors get to a hit on a cached page, WP Super Cache has to performance some logic both in the form of .htaccess (rewrites) and PHP itself (all WP plugins must use php). Whereas FastCGI uses compiled bindings that are fast and routes traffic directly to the cache.
Now, an HTTP cache like Varnish will always be faster than the two. That’s because you’re traveling one fewer hop down the stack to get to the data, which in the case of Varnish sits at the HTTP level as an HTML object and can be served hot.
So to illlustrate:
So to get to the:
FastCGI cache: Nginx -> FastCGI -> File
WP Super Cache cache: Nginx -> FastCGI -> PHP -> File
Varnish cache: HTTP