Traceable performance evaluation: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
This page presents good practices when performing benchmarks using Grid'5000 nodes. It is not about benchmarking Grid'5000 itself. | This page presents good practices when performing benchmarks using Grid'5000 nodes. It is not about benchmarking Grid'5000 itself. | ||
= About the nodes' operating system = | = About the Grid'5000 nodes' operating system = | ||
Grid'5000 nodes can be used with a choice of different system environments: either with the default (standard) environment which is pre-provisioned on nodes, or with a variety of environments deployed on demand by the user. We compare the several options. | Grid'5000 nodes can be used with a choice of different system environments: either with the default (standard) environment which is pre-provisioned on nodes, or with a variety of environments deployed on demand by the user. We compare the several options. | ||
| Line 23: | Line 23: | ||
The recipes from which Grid'5000 environment are built are available in https://gitlab.inria.fr/grid5000/environments-recipes. See [[Environment creation]] for more information about how environments are built. | The recipes from which Grid'5000 environment are built are available in https://gitlab.inria.fr/grid5000/environments-recipes. See [[Environment creation]] for more information about how environments are built. | ||
= About Grid'5000 metering probes = | = About the traceability of the infrastructure = | ||
Special effort is made in Grid'5000 to keep track of infrastructure changes so that any user can get information about for instance what side effects could have impacted an experiment. | |||
* The most notable changes in the infrastructure are the subject of news published on the [[News]] page as well as on the Grid'5000 twitter and sent to the users' mailing list (users@list.grid5000.fr). It is strongly recommended to follow the news. | |||
* Detailed changes in the components of the infrastructure are recorded in the [https://gitlab.inria.fr/grid5000/reference-repository reference repository] (git). Updates of firmware versions for instance are tracked there. | |||
* Changes in the way the operating system of nodes is built are tracked in the [https://gitlab.inria.fr/grid5000/environments-recipes/ environment recipes] git repository. | |||
= About the Grid'5000 metering probes = | |||
Grid'5000 provides the [[Monitoring_Using_Kwollect|kwollect]] service that can collect information about nodes during a job: energy, network traffic, and more. See the [[Monitoring_Using_Kwollect|kwollect]] page or the [[Energy consumption monitoring tutorial]]. | Grid'5000 provides the [[Monitoring_Using_Kwollect|kwollect]] service that can collect information about nodes during a job: energy, network traffic, and more. See the [[Monitoring_Using_Kwollect|kwollect]] page or the [[Energy consumption monitoring tutorial]]. | ||
Revision as of 13:33, 15 September 2021
This page presents good practices when performing benchmarks using Grid'5000 nodes. It is not about benchmarking Grid'5000 itself.
About the Grid'5000 nodes' operating system
Grid'5000 nodes can be used with a choice of different system environments: either with the default (standard) environment which is pre-provisioned on nodes, 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 uninstall/deactivate 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 remove package) or just deactivated (with systemctl stop service) after becoming root (with sudo-g5k).
The following services are known to possibly impact benchmarks:
- prometheus-node-exporter.service: metrics polled every 15 seconds
- ...
Also, the Grid'5000 default environment includes some common system tweaks that may have biases on benchmarks. The CPU parameters page may provide relevant information.
Benchmarking on a deployed environment
Using kadeploy is very relevant for benchmarking, as it allows the user to operate the nodes with the most minimalistic system that is sufficient for the benchmark. For instance, one can deploy the -min variant of one of the Grid'5000 supported environments, or a customized environment possibly built on top of a minimalistic environment and featuring only software required for running the benchmark.
|
Note |
|---|---|
By design, the | |
The recipes from which Grid'5000 environment are built are available in https://gitlab.inria.fr/grid5000/environments-recipes. See Environment creation for more information about how environments are built.
About the traceability of the infrastructure
Special effort is made in Grid'5000 to keep track of infrastructure changes so that any user can get information about for instance what side effects could have impacted an experiment.
- The most notable changes in the infrastructure are the subject of news published on the News page as well as on the Grid'5000 twitter and sent to the users' mailing list (users@list.grid5000.fr). It is strongly recommended to follow the news.
- Detailed changes in the components of the infrastructure are recorded in the reference repository (git). Updates of firmware versions for instance are tracked there.
- Changes in the way the operating system of nodes is built are tracked in the environment recipes git repository.
About the Grid'5000 metering probes
Grid'5000 provides the kwollect service that can collect information about nodes during a job: energy, network traffic, and more. See the kwollect page or the Energy consumption monitoring tutorial.