Merge pull request #343 from csc-training/jobids-to-scalingtest-exercise

extend scaling test exercise
csc-training · Feb 12, 2025 · 19fa915 · 19fa915
2 parents 181f9cd + bdc229e
commit 19fa915
Showing 1 changed file with 20 additions and 13 deletions.
diff --git a/part-2/workflows/tune-performance.md b/part-2/workflows/tune-performance.md
@@ -82,12 +82,12 @@ example simulation.
    Calculate the speedup by dividing the previous elapsed time with the elapsed
    time obtained using twice as many nodes:
 
-   | Number of nodes | Elapsed time (s) | Speedup                         |
-   |:---------------:|:----------------:|:-------------------------------:|
-   |1                |                  | -                               |
-   |2                |                  | *t*<sub>1</sub>/*t*<sub>2</sub> |
-   |4                |                  | *t*<sub>2</sub>/*t*<sub>4</sub> |
-   |8                |                  | *t*<sub>4</sub>/*t*<sub>8</sub> |
+   | Number of nodes | Elapsed time (s) | Speedup                         | SLURM JobID     |
+   |:---------------:|:----------------:|:-------------------------------:|:---------------:|
+   |1                |                  | -                               |                 |
+   |2                |                  | *t*<sub>1</sub>/*t*<sub>2</sub> |                 |
+   |4                |                  | *t*<sub>2</sub>/*t*<sub>4</sub> |                 |
+   |8                |                  | *t*<sub>4</sub>/*t*<sub>8</sub> |                 |
 
 ☝🏻 Remember that the speedup should be *at least* 1.5x when you double the
 number of cores! This is important to ensure that the CPU resources are used
@@ -136,13 +136,13 @@ environment variable to be equal to the number of threads per task.
 
 3. Complete the table below:
 
-   | MPI tasks per node  | OpenMP threads per task | Elapsed time (s) | Memory utilized (GB) |
-   |:-------------------:|:-----------------------:|:----------------:|:--------------------:|
-   |128                  |                         |                  |                      |
-   |64                   |                         |                  |                      |
-   |32                   |                         |                  |                      |
-   |16                   |                         |                  |                      |
-   |8                    |                         |                  |                      |
+   | MPI tasks per node  | OpenMP threads per task | Elapsed time (s) | Memory utilized (GB) | SLURM JobID |
+   |:-------------------:|:-----------------------:|:----------------:|:--------------------:|:-----------:|
+   |128                  |                         |                  |                      |             |
+   |64                   |                         |                  |                      |             |
+   |32                   |                         |                  |                      |             |
+   |16                   |                         |                  |                      |             |
+   |8                    |                         |                  |                      |             |
 
 💭 Were you able to run the calculation faster by launching multiple OpenMP
 threads per MPI task? What is the optimum ratio?
@@ -151,6 +151,13 @@ threads per MPI task? What is the optimum ratio?
 task? Use the `seff` command to check. Can you explain the reason for your
 observation?
 
+Note: if you plan to apply for study credits for this course, prepare a report
+including the tables above and discussion on all questions with the 💭 symbol
+and (upload the report and) present it with the course certificate to the local
+authority granting credits. CSC cannot grant credits but for carefully and
+correct reports we recommend granting them.
+
+
 ## More information
 
 - [Docs CSC: Performance checklist](https://docs.csc.fi/computing/running/performance-checklist/)