---------------------
1) there is maxThreads=100 in context.xml
2) sending 100 simultaneous requests to one servlet, for example ab.exe -n
100 -c 100 {address}
3) in the servlet's own log for performance it shows around only 200-500 ms
per request
4) in the ab.exe log it shows around 7 seconds(!) per request
---------------------
So the question is- is it a some sort of socket level bottleneck?
In JProfiler there is no thread locks shown.
How to resolve it?
====================================================
full log of ab.exe is
====================================================
Concurrency Level: 100
Time taken for tests: 16.656 seconds
Complete requests: 100
Failed requests: 0
Write errors: 0
Total transferred: 2770200 bytes
HTML transferred: 2742700 bytes
Requests per second: 6.00 [#/sec] (mean)
Time per request: 16656.250 [ms] (mean)
Time per request: 166.563 [ms] (mean, across all concurrent requests)
Transfer rate: 162.42 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 31 146 208.0 109 1922
Processing: 1328 8015 4329.2 7797 16250
Waiting: 578 7109 4323.0 6734 15281
Total: 1438 8161 4350.1 7875 16281
Percentage of the requests served within a certain time (ms)
50% 7875
66% 9969
75% 10969
80% 11609
90% 15547
95% 16141
98% 16219
99% 16281
100% 16281 (longest request)
--
View this message in context:
http://www.nabble.com/tomcat6%2C-bottleneck%2C-concurrent-requests%2C-windows-xp-tp20996642p20996642.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
