3 ms·
The part about inability to speed up authenticated page loads fails to take into consideration things like ESI. If the majority of your page is still the same
by stephenr 12y ago
The part about inability to speed up authenticated page loads fails to take into consideration things like ESI.
If the majority of your page is still the same for logged-in users, but they see some pieces of content personalised for them, breaking them out into individually request-able components means you can let software like Varnish or a CDN rely on it's cache of the main page content, and make a very small (and ideally simple to process on the backend) request for the per-user content.
It took me some hunting to find it (no docs for v5 yet apparently) but if your stack already includes a caching layer (e.g. Varnish or a CDN) you may want to disable this extra cache using the config described here: http://blog.phusion.nl/2014/11/25/introducing-phusion-passenger-5-beta-1-codename-raptor/#mc_embed_signup http://blog.phusion.nl/2014/11/25/introducing-phusion-passen...