Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4DC14FC4.3010502@apache.org>
Date: Wed, 04 May 2011 14:08:20 +0100
From: Mark Thomas <markt@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB;
 rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: BIO performance issues
References: <4DC05F39.2060102@apache.org>
	<BANLkTi=fcnnhk6UTx6Ls4qnjHAJsWowFcQ@mail.gmail.com>
	<4DC13D7F.7050705@apache.org>
 <BANLkTikbYabQWyNCeguzB1FtgCEEhY64zQ@mail.gmail.com>
In-Reply-To: <BANLkTikbYabQWyNCeguzB1FtgCEEhY64zQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 04/05/2011 14:03, Konstantin Kolinko wrote:
> 2011/5/4 Mark Thomas <markt@apache.org>:
>> 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.

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org