Differences

This shows you the differences between two versions of the page.

--- doku:monitoring [2022/06/23 13:16]
msiegel
+++ doku:monitoring [2022/06/23 13:22]
msiegel
@@ Line 4: / Line 4: @@
 There are several ways to monitor the threads CPU load distribution of
-your job, either [[doku:monitoring#live | live]] directly on the compute node, or by modifying
+your job, either [[doku:monitoring#Live]] directly on the compute node, or by modifying
 the [[doku:monitoring#Job Script]], or the [[doku:monitoring#Application Code]].
 ==== Live ====
-So we assume your program runs, but could it be faster? SLURM gives you
+So we assume your program runs, but could it be faster? [[doku:SLURM]] gives you
 a ''Job ID'', type ''squeue --job myjobid'' to find out on which node your
 job runs; say n372-007. Type ''ssh n372-007'', to connect to the given
@@ Line 63: / Line 63: @@
 application.
-In the following screenshot we can see stats for all 32 threads of a compute node running ''VASP'':
+In the following screenshot we can see stats for all 32 threads of a compute node running [[doku:VASP]]:
 {{ :doku:top_vasp_2.png }}
@@ Line 82: / Line 82: @@
 === mpi.h ===
-<code C>
+<code cpp>
 #include "mpi.h"
 ...  MPI_Get_processor_name(processor_name, &namelen);
@@ Line 89: / Line 89: @@
 === sched.h (scheduling parameters) ===
-<code C>
+<code c++>
 #include <sched.h>
 ...  CPU_ID = sched_getcpu();
@@ Line 96: / Line 96: @@
 === hwloc.h (Hardware locality) ===
-<code C>
+<code cpp>
 #include <hwloc.h>
 ...