[Seaside] Seaside and Connection Reset by Peer problems

David Carlos Manuelda stormbyte at gmail.com
Tue Feb 17 18:02:30 UTC 2015


I'm stressing test a seaside pharo image with the default configuration by 
using apache's ab benchmark tool.

I have a ZnZincServerAdaptor listenning on port 8080 (created via seaside 
menu GUI).

The problem is that I am starting to receive connection reset by peer when 
the number of concurrent connection grows, which I think can be dangerous on 
a loaded server.

These are the test I've run (default configuration, seaside welcome page)


( SUCCESSFUL )
ab -c 60 -n 5000 http://127.0.0.1:8080/
This is ApacheBench, Version 2.3 <$Revision: 1638069 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 127.0.0.1 (be patient)
Completed 500 requests
Completed 1000 requests
Completed 1500 requests
Completed 2000 requests
Completed 2500 requests
Completed 3000 requests
Completed 3500 requests
Completed 4000 requests
Completed 4500 requests
Completed 5000 requests
Finished 5000 requests


Server Software:        Zinc
Server Hostname:        127.0.0.1
Server Port:            8080

Document Path:          /
Document Length:        4954 bytes

Concurrency Level:      60
Time taken for tests:   13.859 seconds
Complete requests:      5000
Failed requests:        0
Total transferred:      25620000 bytes
HTML transferred:       24770000 bytes
Requests per second:    360.78 [#/sec] (mean)
Time per request:       166.306 [ms] (mean)
Time per request:       2.772 [ms] (mean, across all concurrent requests)
Transfer rate:          1805.31 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0   37 233.8      0    7010
Processing:     7  101 436.7     71   12857
Waiting:        7  101 436.7     71   12857
Total:          8  138 537.0     72   13858

Percentage of the requests served within a certain time (ms)
  50%     72
  66%     83
  75%     87
  80%     88
  90%    104
  95%    216
  98%   1087
  99%   1275
 100%  13858 (longest request)





( FAILING CONNECTIONS )
ab -c 600 -n 5000 http://127.0.0.1:8080/
This is ApacheBench, Version 2.3 <$Revision: 1638069 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 127.0.0.1 (be patient)
Completed 500 requests
Completed 1000 requests
Completed 1500 requests
Completed 2000 requests
Completed 2500 requests
Completed 3000 requests
apr_socket_recv: Connection reset by peer (104)
Total of 3349 requests completed
stormbyte at zero ~ $ ab -c 600 -n 5000 http://127.0.0.1:8080/
This is ApacheBench, Version 2.3 <$Revision: 1638069 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 127.0.0.1 (be patient)
Completed 500 requests
Completed 1000 requests
Completed 1500 requests
Completed 2000 requests
apr_socket_recv: Connection reset by peer (104)
Total of 2097 requests completed






I would appreciate any help or direction so I can configure it better or 
whatever makes me not to be stuck by this anymore as I am out of ideas (at 
first, I thought it was my code, but it is reproducible with "vanilla" 
seaside)

Thanks.



More information about the seaside mailing list