You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Quentin 902555b9d5
Prettier graph
2 weeks ago
csv Add a new benchmark 2 weeks ago
jupyter Add a new benchmark 2 weeks ago
mknet Add other topologies 8 months ago
png Prettier graph 2 weeks ago Add a new benchmark 2 weeks ago
rpc-amplification.R Add a new benchmark 2 weeks ago
rpc-complexity.R Prettier graph 2 weeks ago



This benchmark tests how RPC between nodes having non negligible latency will impact the final S3 request latency.

The idea is that multiple communications must be done over the network between nodes of the cluster to answer an S3 request, and some of them are even sequentials. Depending of the chosen algorithms and implementations, the final S3 request latency will vary.

You need to install first R, R development headers, python3, pip3, wget, iproute2 and maybe some other dependencies. Then run:

sudo ./rpc-amplification.R

you can test a different topology with:

MKNET_DC=./mknet/with-vdsl.yml sudo ./rpc-amplification.R

Generated plot for RPC amplification

This benchmark should be fully automated.


This benchmark validates that the time to complete RPC for a given S3 request is stable when the number of node change. This is not always the case: some distributed protocols send a quadratic number of messages according to the number of nodes.

You need an access to Grid5000. Then import jupyter/rpc-complexity.ipynb in a Grid5000 Jupyter Notebook.

Download all the .csv files in this csv/ folder. And finally run:


Generated plot for RPC complexity

This benchmark is not fully automated.