On Wed, Dec 7, 2011 at 6:39 PM, mpindyala <[email protected]> wrote: > so you are saying max per route cannot be more than maxtotal connections?
Yes. My explanation before was confusing at best. As I understand it, a route is to a specific host. A connection is just a socket. So you can limit both the number of connections you make to a single host, max per route, and the number of overall connections you make to *any* host, max total connections. If you make max per route > max total connections, then max per route will essentially NOT be considered as max total connections will be your limiting factor. > Can I get your httpclient settings for achieving 65k per sec ? it would be > really useful to us. I didn't do anything special. I think I simply had 2000 total connections and max per route (as I was going to the same host). However, the host was on a LAN and had a very quick response. Again, I would enable logging to see exactly what is going on. You often think you're going down the same route, but aren't. Enabling logging will show you when it's allocating a new request, and when it's reusing an existing connection. This will kill your performance, but at least you'll see how the client is behaving and make any changes to your code if needed. Bill- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
