Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to implement apache connection pooling between two apache2 servers. So that there are connections already established and my response time is reduced.

I am aware that we need to use either Worker or Event MPM. I also need to know how to identify the same in log files.

Thanks in advance, Paresh

share|improve this question
I think the goal is not really clear. Do you want a loadbalancing? – Stony Mar 26 '12 at 11:13
i have two servers 1 in uk and the other in us. My http request is sent from UK servers to my clients server in US which takes 300ms to get the response. I have placed a new server in US so that a pool of connection is established between both of my servers such that next time my response time would be less. Since the US and UK server will already have connection established. – user1292364 Mar 26 '12 at 11:43

This started off as a comment but got a bit long.

There is no such thing as connection pooling in HTTP. Transaction pipelining is possible (see HTTP keepalives) but this has nothing to do with the process engine. (SPDY also allows for transaction multiplexing - but that's something different again). Adding servers (appropriately configured) will decrease connection re-use hence worsening your performance.

In addition to what appears to be a flawed premise and incorrect assumptions, you've omitted a lot of information which is relevant - What OS is running at both ends? Are you using SSL? What is your SSL session timeout? Are you using a shared SSL session cache?

If network latency is the big problem here, then running the HTTP through a VPN or IPSEC instead of SSL will improve the situation (no need for SSL [re-]negotiation for every request but you still have a TCP handshake).

If SSL is not a consideration, then make sure you've got window scaling set up properly with appropriate RWINs at both ends. Most OS will cache the slow start threshold across connections which means that it shouldn't have too much impact unless connections between the end-points are relatively infrequent - in which case you might want to set a higher default.

share|improve this answer
On both the ends i have debian 6.0 running. We are not using ssl. Is it possible to reduce TCP handshake. – user1292364 Mar 26 '12 at 13:55
No, youn only reduce the time for TCP handshake by reducing the latency of the network connection. But you can use pipelining and increase the initial cwnd to reduce the slow start impact. – symcbean Mar 26 '12 at 15:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.