On Thu, 2016-10-27 at 15:13 +0200, Joan Balagueró wrote: > Hi Oleg, > > Sorry yes, reviewing emails I already asked about TimeoutException. I've been > reading again the httpcore tutorial because think I had a misunderstanding > about how the async client works. > > In the previous case we had about 1000 requests per second, and the average > response time was about 20ms. So Stefan proposed a pool of 50 connections > with a pool timeout of 10-20ms. > > In the current case we're having not more than 100 requests per second, but > the average response time is 1 second. > > When a connection is established, if no packets are being received, the > IOReactor dispatch thread is released to do another task, but the http > connection continues established. So in the current case, where I have less > concurrency but much longer response times I should set up a higher max > connections. Right? > > If so, just two questions: > > 1. Why, exactly in the same load conditions, a pool with 600 connections is > more than enough for the blocking client and not enough for the async one? >
I cannot answer this question unless I can analyze and re-run the benchmark used to load test both clients. > 2. Regarding the 'ConnectionRequestTimeout', you told me that the reason was > probably due to lock contention. Is this lock contention provoked by this > timeout of only 1ms? Do you always recommend a higher value as Stefan said > previously? > What is the point of having such a low request timeout? What is it exactly you intent to achieve by making requests fail if the pool manager fails to lease a connection after 1 ms? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
