Please visit uperf.org for the latest information
On the slave run
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 firstname.lastname@example.org to discuss uperf issues.
uperf uses the standard GNU build tools (
It is possible to build uperf as a part of AOSP platform. Because autotools are not used in Android platform config.h cannot be generated automatically. A version of config.h for Android N is created manually. Modifications may be required for compatibility with other Android versions.
- Download uperf sources and place them under appropriate AOSP directory, e.g. external/uperf
- Initialize build environment following standard Android steps
source build/envsetup.sh, refer to Android official documentation for this part)
- Build uperf
cd external/uperf mm
- 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
workloads/ directory for example profiles