netdev - Re: Network performance

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BB0D9A1.3090107@hp.com>
Date:	Mon, 29 Mar 2010 09:47:29 -0700
From:	Rick Jones <rick.jones2@...com>
To:	michal.simek@...alogix.com
CC:	LKML <linux-kernel@...r.kernel.org>,
	John Williams <john.williams@...alogix.com>,
	netdev@...r.kernel.org, Grant Likely <grant.likely@...retlab.ca>,
	John Linn <John.Linn@...inx.com>,
	"Steven J. Magnani" <steve@...idescorp.com>,
	Arnd Bergmann <arnd@...db.de>, akpm@...ux-foundation.org
Subject: Re: Network performance - iperf

I don't know how to set fixed socket buffer sizes in iperf, if you were running 
netperf though I would suggest fixing the socket buffer sizes with the 
test-specific -s (affects local) and -S (affects remote) options:

netperf -t TCP_STREAM -H <remote> -l 30 -- -s 32K -S 32K -m 32K

to test the hypothesis that the autotuning of the socket buffers/window size is 
allowing the windows to grow in the larger memory cases beyond what the TLB in 
your processor is comfortable with.

Particularly if you didn't see much degredation as RAM is increased on something 
like:

netperf -t TCP_RR -H <remote> -l 30 -- -r 1

which is a simple request/response test that will never try to have more than 
one packet in flight at a time, regardless of how large the window gets.

happy benchmarking,

rick jones
http://www.netperf.org/
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html