[TYPO3-Performance] ab failed requests

Dan Osipov dosipov at phillyburbs.com
Tue Dec 23 15:13:14 CET 2008


Tried, didn't help:


Server Software:        Apache/2.2.3
Server Hostname:        localhost
Server Port:            80

Document Path:          /
Document Length:        106505 bytes

Concurrency Level:      10
Time taken for tests:   29.289296 seconds
Complete requests:      1000
Failed requests:        992
    (Connect: 0, Length: 992, Exceptions: 0)
Write errors:           0
Total transferred:      106785315 bytes
HTML transferred:       106511315 bytes
Requests per second:    34.14 [#/sec] (mean)
Time per request:       292.893 [ms] (mean)
Time per request:       29.289 [ms] (mean, across all concurrent requests)
Transfer rate:          3560.41 [Kbytes/sec] received

Connection Times (ms)
               min  mean[+/-sd] median   max
Connect:        0    0   0.0      0       0
Processing:   115  291 148.4    282    3298
Waiting:      115  287 148.4    277    3298
Total:        115  291 148.4    282    3298

Percentage of the requests served within a certain time (ms)
   50%    282
   66%    302
   75%    315
   80%    325
   90%    346
   95%    364
   98%    387
   99%    406
  100%   3298 (longest request)

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Martin Scholl wrote:
> Hello all,
> 
> 
> Dan Osipov wrote:
>> Hello all,
>>
>> I've been testing TYPO3 installation under relatively high load, and see 
>> some problems with ab. There are a lot of failed requests. I have Apache 
>> running with mod_fcgid under Debian. The server is fairly fast - 16Gb 
>> RAM, Quad core Xeon processor, etc.
>>
>> Anyone run into a similar issue? I'm pretty sure its my Apache set up, 
>> but I can't pinpoint what exactly is wrong. Its operating well for a few 
>> requests, but as soon as there are several concurrent users, it usually 
>> fails...
>>
>> Here is a typical ab output:
>>
>> Server Software:        Apache/2.2.3
>> Server Hostname:        localhost
>> Server Port:            80
>>
>> Document Path:          /
>> Document Length:        99906 bytes
>>
>> Concurrency Level:      100
> sometimes you don't get an error message in the logfiles. This happens
> when for example there is a connection timeout.
> With such a high concurrency like 100, this can easily happen if you
> haven't optimized your server's software configuration.
> 
> Try it again with a lower concurrency (e.g. 25) again and see what happens.
> 
> 
> Martin
> 
> 
> [snip]


More information about the TYPO3-Performance mailing list