[Dnsmasq-discuss] bad performance with dhcperf

Stefan Krüger stadtkind2 at gmx.de
Wed Jun 18 12:37:00 BST 2008


Hello list,

I did some testing (after fixing some compiler warnings) with dhcperf 
(ftp://ftp.nominum.com/pub/nominum/dhcperf/1.0.1.0/)

Dnsmasq 2.43test6 on Solaris10/sparc

# dhcperf --server solaris --discover (executed on FreeBSD 7)
Wanted 3145728 bytes in output buffer; got 229376.
Wanted 3145728 bytes in input buffer; got 229376.
Beginning DHCPDISCOVER load test.
Initial probe complete: High-water mark is 2 clients/second.
Preparing for next test run.
Beginning test run: 1 clients/second for 120 seconds.
Stopping run after 24 seconds; 1/19 clients failed.
0 five-way handshakes per second.

Same test with ISC's dhcpd (4.1.0a1)

# dhcperf --server solaris --discover
Wanted 3145728 bytes in output buffer; got 229376.
Wanted 3145728 bytes in input buffer; got 229376.
Beginning DHCPDISCOVER load test.
Initial probe complete: High-water mark is 40 clients/second.
Preparing for next test run.
Beginning test run: 20 clients/second for 120 seconds.
Succeeded: 0/2400 clients failed.
Preparing for next test run.
Beginning test run: 30 clients/second for 120 seconds.
Succeeded: 0/3600 clients failed.
Preparing for next test run.
Beginning test run: 35 clients/second for 120 seconds.
Succeeded: 0/4200 clients failed.
Preparing for next test run.
Beginning test run: 37 clients/second for 120 seconds.
[...]

Now the other way around (dnsmasq 2.41 /dhcpd 3.0.5  on FreeBSD 7, 
dhcperf on Solaris)

# /usr/local/nom/bin/dhcperf --server freebsd --discover
Wanted 3145728 bytes in output buffer; got 2097152.
Wanted 3145728 bytes in input buffer; got 2097152.
Beginning DHCPDISCOVER load test.
Initial probe complete: High-water mark is 2 clients/second.
Preparing for next test run.
Beginning test run: 1 clients/second for 120 seconds.
Stopping run after 5 seconds; 1/1 clients failed.
0 five-way handshakes per second.

Now ISC's dhcpd:

# /usr/local/nom/bin/dhcperf --server freebsd --discover
Wanted 3145728 bytes in output buffer; got 2097152.
Wanted 3145728 bytes in input buffer; got 2097152.
Beginning DHCPDISCOVER load test.
Initial probe complete: High-water mark is 26 clients/second.
Preparing for next test run.
Beginning test run: 13 clients/second for 120 seconds.
Succeeded: 0/1560 clients failed.
Preparing for next test run.
Beginning test run: 19 clients/second for 120 seconds.
Succeeded: 0/2280 clients failed.
Preparing for next test run.
Beginning test run: 22 clients/second for 120 seconds.
Succeeded: 0/2640 clients failed.
Preparing for next test run.
[...]

Any ideas why dnsmasq performs so bad (or not at all)?



More information about the Dnsmasq-discuss mailing list