- The following test might require some tuning by the provider to make them work on the purchased cluster. Typos or incorrect syntax in the provided commands do not exempt the provider from passing the tests.
## General definitions
- A test can contain several tasks, and each task may contain several jobs.
- A test may be and stand alone test or contain substests
- A test/subtest can contain several tasks, and each task may contain several jobs.
- We define a task as a collection of jobs which have similar parameters defined in the test.
- A job is an own parallel execution (i.e., using mpi/gpu) to be executed in a unique set of nodes.
@@ -18,8 +19,6 @@
## General considerations:
- All jobs in all tests must successfully excede the minimal performance prerequisite (ns/day) established for the task.
- A test may contain substests
- Tests/subtests may contain several tasks
- All the jobs in a task must run simultaneously and use a the maximum possible number of nodes within the set of nodes specified.
- When executing a task, no time gaps between the submission of jobs are acceptable beyond those produced by the job scheduler when functioning normally.
- If the performance results provided by the client are challenged by the supplier, it is the responsibility of the provider to adjust the minimal instructions provided for each test to run in the cluster in a way that fulfills the target performance.