tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Hanik - Dev" <devli...@hanik.com>
Subject Re: Tomcat in a High Traffic Environment
Date Fri, 29 Oct 2004 15:49:28 GMT
turn off keep alive
----- Original Message ----- 
From: "Andrew Miehs" <andrew@2sheds.de>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Friday, October 29, 2004 10:45 AM
Subject: Re: Tomcat in a High Traffic Environment


Hi Yoav,

I have not read the Servlet Spec, so please pardon my ignorance. 
(Definitely do not mean to offend). What I still haven't had clearly 
answered is:

User A sends request (with keepalive) to tomcat. Tomcat assigns request 
to thread (T1).
Tomcat sends result back. Is thread T1 now kept reserved for user A 
until he/ or tomcat closes the keep-alive connection?

If this is the case, and I now have 1000 users, each with 2 connections 
per user (ie: 2000 connections) do I need 2000 threads? What if the 
requests each only take a very short amount of time? The server is 
capable of answering a lot more requests than those from the 1000 
users, but due to the number of connections and threads, I am limited 
to the 1000 users per machine...

Or am I just missing something here...

I can understand the issue with the one thread one request in the Spec 
- am just wondering if there isn't a better way, as I can not see how 
this can possible scale in a high traffic environment -
or maybe I just don't understand... :-(

Thanks

Andrew

On 29.10.2004, at 17:28, Shapira, Yoav wrote:

>
> Hi,
>
>> these keep-alive connections? Does it really keep 1 thread open for
>> each keep-alive? this seems VERY unnecessary....
>
> Remember that the Servlet Spec mandates the Servlet Container service a
> request with one thread, independent of the HTTP details.  So before 
> you
> think we're clueless when it comes to performant connection handling
> design, please keep that in mind ;)
>
> Yoav
>
>
>
>
> This e-mail, including any attachments, is a confidential business 
> communication, and may contain information that is confidential, 
> proprietary and/or privileged.  This e-mail is intended only for the 
> individual(s) to whom it is addressed, and may not be saved, copied, 
> printed, disclosed or used by anyone else.  If you are not the(an) 
> intended recipient, please immediately delete this e-mail from your 
> computer system and notify the sender.  Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


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

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


Mime
View raw message