Hi,
We've been looking at using Varnish 2.1.5 with ESIs to allow us to cache the
bulk of our page content whilst still generating the user-specific sections
dynamically. The sticking point for us is that some of these page sections
cannot be cached. It seems, based on both observed behaviour and a quick look
at the code for ESI_Deliver, that Varnish is processing and requesting content
for the ESIs serially rather than in parallel.
I know there has been a lot of work on ESIs for Varnish 3, but as far as I can
tell they are still processed serially. Are there any plans to switch to a
parallel processing model? If not, might this be a worthy feature request for a
future version of Varnish?
Cheers,
Steve
--
Steve Webster
Web Architect
LOVEFiLM
-----------------------------------------------------------------------------------------------------------------------------------------
LOVEFiLM UK Limited is a company registered in England and Wales.
Registered Number: 06528297.
Registered Office: No.9, 6 Portal Way, London W3 6RU, United Kingdom.
This e-mail is confidential to the ordinary user of the e-mail address to which
it was addressed. If you have received it in error,
please delete it from your system and notify the sender immediately.
This email message has been delivered safely and archived online by Mimecast.
For more information please visit http://www.mimecast.co.uk
-----------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________
varnish-misc mailing list
[email protected]
http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
