4 ms·
Ah, yes, if your site is uncachable anyway, then that really is the way to go. Caching two copies isn't unreasonable I guess, but in the context of Rails (which
by JangoSteve 16y ago
Ah, yes, if your site is uncachable anyway, then that really is the way to go. Caching two copies isn't unreasonable I guess, but in the context of Rails (which is the unstated context of this solution), it's more of a pain in the ass than it's worth.
[Edit: I updated the post to be clear that this solution does work if your page is uncachable anyway.]
- aaronblohowiak 16y agoThis is a big win when you use ESI, so your actual page content is cached separately from your header information. You can even push the decision about which asset links to use out to the edge. Goooooo Varnish!
- j15e 16y ago/agree "I won’t go into detail about how to actually accomplish this, because the truth is, this won’t work either. " => the truth is.. you fail ;) But yeah, nice loading graph and +1 for the mathematical/logical alternative solution. Good article