We're noticing around a 150ms overhead and ALL calls (GETs, POSTs, etc)
when using HTTPClient (tried everything between 2.0 alpha 3 and 2.0
RC1). The strange thing is that sometimes those overheads drop down to
5ms, which is much better and what we expect. Unfortunately, we haven't
been able to pinpoint _why_ those drops take place yet.
We've played with various app servers (Resin 2.x and Tomcat 4.1.x),
using various connectors and connection pools, and nothing seems to help
out here. We're using HTTP 1.1 and keep alives, and the server and
client are on the same machine so network latency is not an issue.
If I use nogoop's HTTP Client or even the JDK's URLConnection, I can get
responses back around 5ms like I'd expect. Has anyone experienced
something like this? Any thoughts as to what is going on with
HTTPClient?
-Pat
