Scenario configuration#
A test scenario is a set of tests with specific dependencies between them. A test scenario is described in a TOML schema file. The following is an example of a test scenario file:
name = "nccl-test"
[[Tests]]
id = "Tests.1"
test_name = "nccl_test_all_reduce"
num_nodes = 2
time_limit = "00:20:00"
[[Tests]]
id = "Tests.2"
test_name = "nccl_test_all_gather"
num_nodes = 2
time_limit = "00:20:00"
[[Tests.dependencies]]
type = "start_post_comp"
id = "Tests.1"
[[Tests]]
id = "Tests.3"
test_name = "nccl_test_reduce_scatter"
num_nodes = 2
time_limit = "00:20:00"
[[Tests.dependencies]]
type = "start_post_comp"
id = "Tests.2"
The scenario name identifies the experiment. Each [[Tests]] entry has a unique id.
Use test_name to select a definition from the test directory, or place the workload definition directly in the entry.
See Understand experiment configuration for the smaller inline form.
Select nodes#
Choose one allocation form in a [[Tests]] entry:
Selection |
TOML |
|---|---|
Node count |
|
Explicit nodes |
|
Configured group |
|
All available nodes in a group |
|
Replace node and group names with entries for your system. Explicit node lists let Slurm apply arbitrary task placement.
Set time_limit in Slurm format when required.
Coordinate cases#
Without dependencies, cases may execute concurrently, subject to resources and runner behavior.
Add dependencies inside the dependent [[Tests]] entry:
[[Tests.dependencies]]
type = "start_post_comp"
id = "Tests.1"
Type |
Behavior |
|---|---|
|
Start after the referenced case begins, with a specified delay. |
|
Start after the referenced case completes. |
|
End when the referenced case completes. |