I'm using Varnish as a frontend with Apache 2 as backend on my web server. What are the pros and cons of Apache's
KeepAlive in this setting?
Apache and Varnish run on the same server now, but I could put them on different servers in the future.
Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.Sign up to join this community
Can you clarify what's prompting this question? HTTP connection keep-alive is implied in HTTP 1.1 and on by default in every major web server for a good reason; it's a performance improvement (though it will be a very small one with no latency between services), with a couple of denial-of-service-related caveats that aren't applicable when Apache's only client is Varnish.
I'd even recommend increasing Apache's
KeepAliveTimeout higher than the default of 5 seconds, to let Varnish continue to re-use the same pool of connections.