Darryl Miles wrote:
LOL. Each HTTP request/response cycle is handed off to a worker
thread, the available worker threads are dynamically increased to cope
with the number of the simultaneous HTTP requests being processed in
the moment.
But isn't it Java threads. I'm speaking of operating system threads.
ps aux
Biernatowski, Is your HTTP application multi-threaded ?
Irrelevant. Unimportant.
What is the nature of the application, when you say there is a
performance bottleneck how are you measuring it and what is the nature
of the workload each request is doing.
It is important. Where is your bottleneck?
There is a big difference between getting tomcat to serve static
content and making your servlet do long running SQL jobs.
Or to have i.e. extremely large Lucene database or some other slow
algorithm.
--
Mladen Adamovic
http://www.online-utility.org http://www.shortopedia.com
http://www.froola.com http://www.gift-idea4u.com
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
