|Quentin 902555b9d5||1 year ago|
|csv||1 year ago|
|jupyter||1 year ago|
|mknet||2 years ago|
|png||1 year ago|
|README.md||1 year ago|
|rpc-amplification.R||1 year ago|
|rpc-complexity.R||1 year 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:
you can test a different topology with:
MKNET_DC=./mknet/with-vdsl.yml sudo ./rpc-amplification.R
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.
Download all the
.csv files in this
And finally run:
This benchmark is not fully automated.