See a pretty graph showing performance of ifconfig and ip
both with and without my device-hashed-lookup patch:
(If you can't get to it, let me know and I'll email it to you...some
cable modem networks have I firewalled.)
I ran ifconfig -a and ip addr show every 50 interfaces,
as I added 4000 interfaces, and used the 'time -p' program to
find the system and user times.
ifconfig scales badly, ip is better.
Both ip and ifconfig work better with the hash patch, at
least when the number of interfaces grows past 1000.
If anyone wants the raw numbers, I can provide them and the script
that generated them.
NOTE: I stopped the non-hashed test after 3000 interfaces because
it was just going too slow (ifconfig was killing me!)
So, is this good enough reason to add the hashed patch?
If not, I feel sure I can write a program that binds to a specific
interface 10k times, and my assumption is that the hash will help
significantly if there are lots of interfaces. However, I'd
rather not go to the hassle if the ifconfig/ip numbers are sufficient.
If no amount of benchmarking will change key player's minds, then
go ahead and tell me now so that I can go back to hacking code
and just include this patch with my VLAN patch.
Ben Greear (greearb@xxxxxxxxxxxxxxx) http://www.candelatech.com
Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL)