Opened 8 years ago
#710 new defect
Second run of ApacheBench against HelenOS websrv times out
| Reported by: | Jakub Jermář | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | helenos/net/tcp | Version: | mainline |
| Keywords: | tcp, websrv | Cc: | |
| Blocker for: | Depends on: | ||
| See also: | #515 |
Description
As of 75fcf9b27, running the testcase from #515 results in a timeout for the second run (make sure to start websrv in HelenOS before running this):
bash-4.4$ ab -c 4 -n 10 -t 30 -g results.out http://localhost:8080/index.html
This is ApacheBench, Version 2.3 <$Revision: 1807734 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)
Finished 130 requests
Server Software:
Server Hostname: localhost
Server Port: 8080
Document Path: /index.html
Document Length: 478 bytes
Concurrency Level: 4
Time taken for tests: 30.032 seconds
Complete requests: 130
Failed requests: 0
Total transferred: 64610 bytes
HTML transferred: 62140 bytes
Requests per second: 4.33 [#/sec] (mean)
Time per request: 924.057 [ms] (mean)
Time per request: 231.014 [ms] (mean, across all concurrent requests)
Transfer rate: 2.10 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 68 921 784.7 777 2596
Waiting: 47 894 772.3 751 2550
Total: 68 921 784.6 777 2596
Percentage of the requests served within a certain time (ms)
50% 777
66% 1233
75% 1589
80% 1787
90% 2079
95% 2317
98% 2519
99% 2532
100% 2596 (longest request)
bash-4.4$ ab -c 4 -n 10 -t 30 -g results.out http://localhost:8080/index.html
This is ApacheBench, Version 2.3 <$Revision: 1807734 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)
apr_pollset_poll: The timeout specified has expired (70007)
Total of 116 requests completed
Even after the second run ends with the above error, top shows there is still some activity happening inside tcp.
Note:
See TracTickets
for help on using tickets.
