d/iperf3-tls
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

added explaination of 'typical' mode vs 'extreme performance' mode

Browse Source
This commit is contained in:
Brian Tierney 2013-12-04 13:59:06 -08:00
parent 95360b2046
commit e42991a717
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README
View File

@ -63,5 +63,14 @@ For sample command line usage, see:
http://fasterdata.es.net/performance-testing/network-troubleshooting-tools/iperf-and-iperf3/
Using the default options, iperf is meant to show typical well designed application performance.
'Typical well designed application' means avoiding artificial enhancements that work only for testing
(such as splice()'ing the data to /dev/null). iperf does also have flags for 'extreme best case'
optimizations but they must be explicitly activated.
These flags include:
-Z, --zerocopy use a 'zero copy' sendfile() method of sending data
-A, --affinity n/n,m set CPU affinity