tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johnny Kewl" <j...@kewlstuff.co.za>
Subject Re: Tomcat Threads handling user Requests problem
Date Mon, 02 Jul 2007 18:04:18 GMT
Here, I found a link so you can read about the PIPE stuff I'm waffling on 
about
http://www.w3.org/Protocols/HTTP/Performance/

and it also give you a way to change it...
If you trick Tomcat into making it think its a HTTP/1.0 connection.... dont 
ask me how but I imagine you can set the Ajax headers somewhere... then I 
think you will see multiple connections..... but as the tests show.... 
HTTP/1.1 is probably faster anyway, and your server will probably fall over 
on high volumes.....


----- Original Message ----- 
From: "Johnny Kewl" <john@kewlstuff.co.za>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Monday, July 02, 2007 7:34 PM
Subject: Re: Tomcat Threads handling user Requests problem


> Can you believe that, IE only allows 2 files downloaded at the same time, 
> and then you have to dig into the registry.... get OPERA ;)
> Now that I advertised my favorite browser....
> I think its working and I have yet another theory ;)
> Modern browsers dont drop the connection, because establishing a 
> connection is very expensive.... so effectively they make a pipe to the 
> server, get the page, then suck down the images, and all the rest of it 
> thru the "same" pipe... assuming that stuff is all on the same server.
> Think they call that stuff KEEP ALIVES, in general, its faster.
> So in fact I think that software is being very smart... its making one 
> pipe for the browser and all the images and stuff.... and another pipe for 
> the XMLHttpRequest, regardless of how many calls the script makes.... its 
> probably faster than if a connection was made for everything in the web 
> page and every script call.... and when you have 200 people using that 
> page at the same time, I think you going to be very happy its only 2 and 
> not 100 connections per page.
> Ajax design has to be done smartly.... you have to have something that 
> keeps the users attention while you populate a table are whatever.... 
> otherwise they will get the urge to click again.
>
> So yes try that.... increase the connections on IE.... 
> http://blogs.msdn.com/ie/archive/2005/04/11/407189.aspx  but I have a 
> feeling it wont change.
> Or.... get Opera, I think it defaults to 8 connections to one server, and 
> 20 max..... dont think it will change, but you just going to be happier 
> anyway ;)
>
>
>
> ----- Original Message ----- 
> From: "Mirek Kopriva" <mirek1977@gmail.com>
> To: <users@tomcat.apache.org>
> Sent: Monday, July 02, 2007 3:55 PM
> Subject: Tomcat Threads handling user Requests problem
>
>
>> Dear All,
>> I have a problem when too few (only 2) Tomcat's threads is handling my
>> requests.
>> First a little background on what I'm trying to do:
>> I have an web application, which loads a page. On loading the page there 
>> are
>> Ajax script calls (DWR framework),
>> requesting more data from the tomcat to be included into the calling page
>> dynamically.
>>
>> There can be as many as 100 separate requests (not usual but possible) 
>> per a
>> page load via Ajax. Some of those
>> requests can take a while because of waiting for another application, I'm
>> trying to integrate with.
>>
>> Now the problem. I can see only 2 Tomcat Threads, handling all of these
>> request, which as you can imagine can take a while.
>> Shouldn't tomcat take a new Thread from the Thread Pool for each Request 
>> up
>> to Maximum? Am I missing some configuration Tricks?
>> Here is the thread pool configuration taken from the Manager.:
>> Any Pointers/Suggestions/Tips would be greatly appreciated,
>> Best Regards,
>> Mirek
>>
>> Max threads: 150 Min spare threads: 25 Max spare threads: 75 Current 
>> thread
>> count: 25 Current thread busy: 4
>> Max processing time: 226598 ms Processing time: 263.88 s Request count: 
>> 75
>> Error count: 14 Bytes received: 0.00 MB Bytes sent: 15.47 MB
>>  Stage Time B Sent B Recv Client VHost Request *S* 8775 ms 0 KB 0 KB
>> 127.0.0.1 localhost POST
>> /cmf/dwr/call/plaincall/FileDetailsDWRHelper.getFileChange.dwr
>> HTTP/1.1 *S* 2146
>> ms 0 KB 0 KB 127.0.0.1 localhost GET /manager/status HTTP/1.1 *R* ? ? ? ? 
>> ?
>> ? *R* ? ? ? ? ? ? *S* 245751 ms 0 KB 0 KB 127.0.0.1 localhost POST
>> /cmf/dwr/call/plaincall/FileDetailsDWRHelper.getFileChange.dwr HTTP/1.1 
>> *R*
>> ? ? ? ? ? ?
>>
>> P: Parse and prepare request S: Service F: Finishing R: Ready K: 
>> Keepalive
>>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message