Traceable performance evaluation

From Grid5000
Revision as of 16:30, 8 September 2021 by Pneyron (talk | contribs) (Created page with "This page presents good practices when performing benchmarks using Grid'5000 nodes. It is not about benchmarking Grid'5000. = About the nodes system = Grid'5000 nodes can be...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This page presents good practices when performing benchmarks using Grid'5000 nodes. It is not about benchmarking Grid'5000.

About the nodes system

Grid'5000 nodes can be used with different environments: either with the default (standard) environment which is pre-provisioned on node, or with a variety of environments deployed on demand by the user. We compare the several options.

Benchmarking on node running the default (standard) environment

In this case, access to the system of the node does not require a deployment (kadeploy), so access is quicker. The system however comes with a lot of functionalities that may impact benchmarks. It may be relevant to stop them before running the benchmark.

The list of services running on the system can be shown using systemctl

Services can be uninstalled (e.g. with apt-get) or just deactivated (with systemctl stop service) after becoming root (with sudo-g5k).

The following services is known to possibly impact benchmarks:

  • ...
  • ...

Benchmarking on an environment deployed on demand