[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: network performance
- To: Andrew Thompson <thompsa_(_at_)_FreeBSD_(_dot_)_org>
- Subject: Re: network performance
- From: Stefan Lambrev <stefan_(_dot_)_lambrev_(_at_)_moneybookers_(_dot_)_com>
- Date: Mon, 04 Feb 2008 23:16:48 +0200
- Cc: freebsd-performance_(_at_)_freebsd_(_dot_)_org
Andrew Thompson wrote:
The traffic, that I generate is with random/spoofed src part, so it is
split between interfaces for sure :)
On Mon, Feb 04, 2008 at 05:26:35PM +0200, Stefan Lambrev wrote:
In my desire to increase network throughput, and to be able to handle more
I started experimenting with lagg and link aggregation control protocol
To my surprise this doesn't increase the amount of packets my server can
Using lagg doesn't improve situation at all, and also errors are not
Also using lagg increased content switches:
Top showed for CPU states +55% system, which is quite high?
I'll use hwpmc and lock_profiling to see where the kernel spends it's time.
Thanks for investigating this. One thing to note is that ip flows from
the same connection always go down the same interface, this is because
Ethernet is not allowed to reorder frames. The hash uses
src-mac, dst-mac, src-ip and dst-ip (see lagg_hashmbuf), make sure when
performance testing that your traffic varies in these values. Adding
tcp/udp ports to the hashing may help.
Here you can find results when under load from hwpmc and lock_profiling:
freebsd-performance_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-performance-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org