Inets performance

Mickael Remond mickael.remond@REDACTED
Tue Mar 6 18:33:40 CET 2001


Hello,

I am doing some benchmarks comparing Apache and Inets 2.5.3 with ab
(Apache benchmark tool).

I made all the tests with ab lauching 5000 connections in a row, using
50 simultaneous connections.

I found some interesting results: 

1. The test client is on the _same_ machine than the Web server:
Inets: 240 requests per second (classic Apache/Debian index.html)
Apache: 540 requests per second (classic Apache/Debian index.html)

2. The test client is on a _different_ machine than the Web server:
Inets: 205 requests per second (classic Apache/Debian index.html)
Apache: 182 requests per second (classic Apache/Debian index.html)

Hum. This is very interesting... From what I understand, Apache seems
to make a better use of the kernel capability for local connections, but
Inets performs nearly the same via the network or on the local machine.

3. The test client is on a _different_ machine than the Web server and I
am using a bigger html file (60ko):
Inets: 9 requests per second
Apache: 17 requests per second

Apache is doing better than Inets for large file.
Do you have any idea of why is there such a difference for large file ?

Do you see anything useful to improve Inets performance for large file ?

Thank you for your help.

-- 
Mickaël Rémond




More information about the erlang-questions mailing list