Re: [AOLSERVER] Mention of AOLserver in Feb 2004 Linux Journal.
<jim <at> rubylane.com>
2004-01-09 14:23:55 GMT
Mathopd will have higher latency as an image server, because it is
single threaded and doesn't do asynchronous disk I/O. So on a
high-end server, the number of IOs/sec it can generate is limited. AS
does not have this problem since it is multi-threaded.
However, mathopd services requests in a very "fair" manner: in an ab
test, the difference between minimum request time and maximum request
time is very small. On AS, this is not the case, and there are
relatively large variances in request service time, indicating that
some threads are being starved. This could be an AS design issue or
an OS scheduling/resource issue - dunno.
Mathopd is definitely the faster engine, but its design limits its
capacity. Mathopd with asynchronous disk I/O would be awesome.
Concurrency Level: 15
Time taken for tests: 0.976 seconds
Complete requests: 10000
Failed requests: 0
Total transferred: 2100210 bytes
HTML transferred: 450045 bytes
Requests per second: 10245.90
Transfer rate: 2151.85 kb/s received
Connnection Times (ms)
min avg max
Connect: 0 0 1
Processing: 0 0 1