Benchmark flist

[AbdelrahmanElawady]

A benchmark flist used as VMs deployed by the Spawner should have the following characteristics:

• Run the following benchmarks periodically and shouldn't be frequent as to not affect the nodes performance for other users:
  • CPU benchmarks using cpu-bench.
  • I/O benchmarks using fio.
  • Network benchmarks using iperf3.
• Push benchmarks results to Aggregator service:
  • A simple program (Go) that is configured with Aggregator URL, token and node ID.
  • Parse relevant data from benchmarks (could be by reading files output by benchmarks or running the benchmarks from the program itself).
  • Push data to Aggregator with the token.

Benchmarks tools mentioned here are just starting points, other might be more suitable.

A simple script for creating a CPU and I/O benchmark flist based on Alpine can be found here.

[AbdelrahmanElawady]

added to tf-images here. Just missing network benchmarks. Also, jq and curl was used to push benchmark results instead of writing a program for that.