[Dnsmasq-discuss] bad performance with dhcperf
simon at thekelleys.org.uk
Wed Jun 18 13:55:42 BST 2008
I downloaded dhcperf and tried it myself with --no-ping set.
It looks like when dhcperf says a test "failed" that means is didn't get
a reply dues to congestion - a real client would retry in this circumstance.
With dnsmasq running on a 733 Mhz Celeron, dhcperf running on a 1.6Ghz
laptop, and a 100Mb/s ethernet between the two, dhcperf settled on 28
five-way handshakes per second as the maximum rate that could be
sustained without any packet loss ( with --no-ping). Without --no-ping I
see similar results to Stefan.
I wonder if the ping timeout is longer than dhcperf is expecting? That
would explain why nearly everything fails when ping is in use.
More information about the Dnsmasq-discuss