On 19 Aug 2002, Ian Holsman wrote:
> The other thing to remember is that in >our< case (yours may vary)
> connection setup/teardown may account for ~10ms, while the actual
> thing being reversed proxied is a order of magnitude (or more)
> larger, and this stuff just gets lost in the noise.
It is not just about response time overhead for connection setup. One
should also account for the number of open connections that need to be
supported (on the proxy and on the origins), related DoS attacks, and
such. I am not saying persistency and "multiplexing" is a big
performance win by default. It may be, in some situations, with proper
tuning.
Alex.
--
| HTTP performance - Web Polygraph benchmark
www.measurement-factory.com | HTTP compliance+ - Co-Advisor test suite
| all of the above - PolyBox appliance
