I've attached two test runs NIO vs BIO.
The results are very similar, in a regular scenario, blocking IO should
be a little bit faster, cause it doesn't have to poll, and then hand off
to a separate thread before reading.
Benefit of the NIO is of course that the number of open sockets are no
longer limited by thread count.
Remy, can you run your tests again, are you still seeing a huge difference?
thanks
Filip
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
That's unfortunate. So regular is better? What are they doing with
Grizzly?
no, its me :)
I need to come up with a non cpu sucking wait algorithm for the wait.
once that is fixed, the performance should be close to identical
For some reason, the performance went down further for me with that
patch (although I noticed the CPU is being used properly this time,
while before Tomcat was not using all the CPU available).
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Filip Hanik
This is ApacheBench, Version 2.0.41-dev <$Revision: 1.2 $> apache-2.0
Copyright (c) 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright (c) 1998-2002 The Apache Software Foundation, http://www.apache.org/
Benchmarking 192.168.3.105 (be patient)
Server Software: Apache-Coyote/1.1
Server Hostname: 192.168.3.105
Server Port: 8081
Document Path: /tomcat.gif
Document Length: 1934 bytes
Concurrency Level: 10
Time taken for tests: 2.187500 seconds
Complete requests: 20000
Failed requests: 0
Write errors: 0
Keep-Alive requests: 19806
Total transferred: 43279030 bytes
HTML transferred: 38680000 bytes
Requests per second: 9142.86 [#/sec] (mean)
Time per request: 1.094 [ms] (mean)
Time per request: 0.109 [ms] (mean, across all concurrent requests)
Transfer rate: 19320.69 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 0 1 3.8 0 31
Waiting: 0 1 3.8 0 31
Total: 0 1 3.8 0 31
Percentage of the requests served within a certain time (ms)
50% 0
66% 0
75% 0
80% 0
90% 0
95% 15
98% 15
99% 15
100% 31 (longest request)
This is ApacheBench, Version 2.0.41-dev <$Revision: 1.2 $> apache-2.0
Copyright (c) 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright (c) 1998-2002 The Apache Software Foundation, http://www.apache.org/
Benchmarking 192.168.3.105 (be patient)
Server Software: Apache-Coyote/1.1
Server Hostname: 192.168.3.105
Server Port: 8080
Document Path: /tomcat.gif
Document Length: 1934 bytes
Concurrency Level: 10
Time taken for tests: 2.62500 seconds
Complete requests: 20000
Failed requests: 0
Write errors: 0
Keep-Alive requests: 19802
Total transferred: 43279240 bytes
HTML transferred: 38680000 bytes
Requests per second: 9696.97 [#/sec] (mean)
Time per request: 1.031 [ms] (mean)
Time per request: 0.103 [ms] (mean, across all concurrent requests)
Transfer rate: 20491.64 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 0 0 5.8 0 93
Waiting: 0 0 5.6 0 93
Total: 0 0 5.8 0 93
Percentage of the requests served within a certain time (ms)
50% 0
66% 0
75% 0
80% 0
90% 0
95% 0
98% 15
99% 15
100% 93 (longest request)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
