@@ -65,8 +65,7 @@ Tests 1.1 - 1.4 test performance scaling over multple nodes over the low-latency
Each test consists of several tasks, defined by the "scaling factor", which is the number of computational nodes involved in each gromacs job.
The number of computational nodes per job in each task will be set to [1, 2, 4, 6, 8, 10, 12, 14, 16, 18 and 20] nodes (limited to the delivered number of nodes in tests 1.2 and 1.4.). Multiple jobs per task will be launched simultaneously such that the partition (cpu / bigmem / gpu / big-gpu) is filled as much as possible.
The number of computational nodes per job in each task will be set to [1, 2, 4, 6, 8, 10, 12, 14, 16, 18 and 20] (limited to the delivered number of nodes in tests 1.2 and 1.4.). Multiple jobs per task will be launched simultaneously such that the partition (cpu / bigmem / gpu / big-gpu) is filled as much as possible.
The following results were obtained for the current cluster (2 x Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz per node).
@@ -75,8 +74,13 @@ The following results were obtained for the current cluster (2 x Intel(R) Xeon(R
**Minimal required performance for passing each of the tests 1.1-1.4:**
For each job, the results for the same number of nodes with the number of cores per node restricted to 36 should be at least 80% of the value obtained with our older aurum cluster, in the table above. For example, a job involving 10 nodes (360 cores) must report at least 0.8*104 = 83.2 ns/day.
**Minimal required performance**
Each job (in every task in all tests 1.1-1.4) must report at least the following performance
Note that this corresponds to the **80%** of the performance recorded in the older aurum cluster (2 x Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz per node).
**Aditional notes**
- Only 36 cores can be used for each node in this test.