tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: BIO performance issues
Date Wed, 04 May 2011 13:08:20 GMT
On 04/05/2011 14:03, Konstantin Kolinko wrote:
> 2011/5/4 Mark Thomas <>:
>> On 04/05/2011 12:04, Konstantin Kolinko wrote:
>>> I do not quite get what happens in 6s. My first understanding from
>>> reading the scenario was that the threads at 2s are busy because we
>>> need them to process keep-alive connections. Then I see that at 6s
>>> keep-alive connections are in the Queue.
>>> What prevents those connections that exist at "2s" from being placed
>>> in the Queue?
>> The keep-alive state is as viewed by the client. At 6s the requests in
>> the queue are open connections that have already processed one requests
>> and therefore are in HTTP keep-alive. However, there are no free threads
>> to process them. If any data was to turn up on those connections they
>> would sit in the queue until a thread was available.
>> The difference between "Allocated threads. In HTTP keep-alive Xs" and
>> "Queued. In HTTP keep-alive for Xs" is that in the allocated case, data
>> will be processed as soon as it arrives.
> Maybe they can be put into the queue, if there is no data after small
> timeout? In your scenario they were waiting for 3s.

That is simulated polling. It works, but with the associated increase in
CPU usage.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message