Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Does anyone know of an overview or comparision table of the common HTTP intermediaries (caches) such as Squid, Varnish, TrafficServer,…?
I am looking in particular for information about their request handling approach (sync vs async, multi-process, multi-threaded etc.)
(I am investigating options I have with regards to ESI. Where my ESI-approach might involve executing a substantial amount of logic during request handling)
Jan
One of the big complaints I’ve read so far is that Varnish processes (replaces) the ESI parts of a (cached) response sequentially. I’m not aware of a concurrent processing implementation, but it would be interesting to see a comparison of the solutions.