Please visit uperf.org for the latest information
On the slave run ./uperf -s
On the master (System under test) ./uperf -m netperf.xml
To get lots of statistics, use the -a option. For ex
./uperf -m netperf.xml -a
Join uperf-devel@lists.sourceforge.net to discuss uperf issues.
Comments/Bugs to realneel@gmail.com or to uperf-devel@lists.sourceforge.net
uperf uses the standard GNU build tools (./configure;make)
- The ./uperf can be run as either a master(active) OR slave(passive).
- When run as active it needs master flag(-m) with a profile describing the test application. Sample profiles have been provided which are sure to run, more and more application profiles are expected to be added defining the various test cases.
- When run as the slave the program needs -s flag
- By default we are using 20000 port as the master port.
- We can set the verbose level, three level are provided
- (-V) High - all the messages are printed
- (-v) med - warnings and critical messages are displayed
- ( ) low - only critical messages are displayed.
- Outputs: See usage for more information
Please see workloads/ directory for example profiles