Run performance tests on network and system software by running snippets of bash scripts on a cluster following a simple definition file. For instance, the following configuration to test iPerf2 performance:
%info
IPerf 2 Throughput Experiment
%config
n_runs=5
var_names={PARALLEL:Number of parallel connections,WINDOW:Window size (kB),THROUGHPUT:Throughput}
%variables
PARALLEL=[1-8]
WINDOW={16,512}
TIME=2
%script@server
iperf -s
%script@client delay=1
//Launch the program, copy the output to a log
iperf -c ${server:0:ip} -w ${WINDOW}k -t $TIME -P $PARALLEL 2>&1 | tee iperf.log
//Parse the log to find the throughput
result=$(cat iperf.log | grep -ioE "[0-9.]+ [kmg]bits" | tail -n 1)
//Give the throughput to NPF through stdout
echo "RESULT-THROUGHPUT $result"When launching NPF with:
npf-run --test tests/tcp/01-iperf.npf \
--cluster client=machine01.cluster.com server=machine02.cluster.comNPF will automatically produce the following graph. Configuration options enable you to change the graph type and many other options easily. check the wiki to see different graphs displaying the same data.
Test files allow to define a matrix of parameters to try many combinations of variables (see here for a description of the possible definitions such as values, ranges, ...) for each test and report performance results and evolution for each combination of variables.
Finally, a graph will be built and statistical results may be computed for each test showing the difference between variable values, different software, or the evolution of performances through commits.
Test files are simple to write, and easy to share, as such we encourage users to share their ".npf" scripts with their code to allow other users to reproduce their results and graphs.
NPF supports running the given test across a cluster, allowing to try your tests in multiple different configurations very quickly and on serious hardware.
The documentation is available on read the docs!
NPF is built using Python 3, and is published on pypi, so it can be installed with pip using:
pip3 install --user npfAt run-time, NPF uses SSH and can benefit from usage of sudo and NFS, see the run-time dependencies in the documentation for more information.
We provide a Dockerfile to use npf.
docker build --tag npf .
docker run -it npf npf-compare ...Your .npf test file is composed of a series of sections, as in the example given above. The sections describe the scripts to run, where to run them, what variables should be tested, what are their ranges, configuration parameters such as timeout or graph colors, etc. Each section is described in more detail in the "writing test script" documentation.
When launching NPF, you will also give the name of one or more repositories, which are files located in the repo folder describing software to download, install and compile so everything is in place when your experiment is launched. They follow a format described in repo/README.md. It can also be ignored using the local fake repository.
Your test script will also define a few script roles, such as client or server as in the example above. When you actually launch your experiment, you must tell which machine (physical or virtual) will take the role. For simple cases, passing the address of a machine with the --cluster role=machine will be enough. When you'd like to define parameters such as IPs and MAC addresses, you can define a cluster file that will describe details about each machine. See the cluster documentation for more details.
Have you read the writing tests documentation? Then, inspire yourself from the test script files in tests/, and write your own!
We welcome merge requests for generic stuffs! But you can keep your files in your "experimentation" folder. Indeed, NPF will always look for a file first in "./repo" for repo files, "./modules" for modules, and "./cluster" for machine definition.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent