Skip to Content

Changes for page Slurm

Last modified by Thomas Coelho (local) on 2025/03/18 13:17
From version 5.1
edited by Thomas Coelho
on 2022/12/08 11:05
Change comment: There is no comment for this version
To version 9.1
edited by Thomas Coelho (local)
on 2025/03/18 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.thw
1 +XWiki.coelho
Content
... ... @@ -14,12 +14,8 @@
14 14  
15 15  A partition is selected by '-p PARTITIONNAME'.
16 16  
17 -|=**Partition** |=**No. Nodes** |=**Cores/M** |=**Tot. Cores**|=**RAM/GB** |=**CPU** |=**Remark/Restriction**
17 +|=**Partition** |=**No. Nodes** |=**Cores/M** |=**Tot. Cores**|=**RAM/GB/;** |=**CPU** |=**Remark/Restriction**
18 18  |itp |10|20 |200|64 |Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz|Common Usage
19 -|dfg-big|3|32|96|128|8-Core AMD Opteron(tm) Processor 6128|Group Valenti
20 -|dfg-big|3|48|144|128/256|12-Core AMD Opteron(tm) Processor 6168|Group Valenti
21 -|dfg-big|4|64|256|128/256|16-Core AMD Opteron(tm) Processor 6272|Group Valenti
22 -|dfg-big|4|48|192|128/256|12-Core AMD Opteron(tm) Processor 6344|Group Valenti
23 23  |fplo|2|12|24|256|Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz|Group Valenti
24 24  |fplo|4|16|32|256|Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz|Group Valenti
25 25  |dfg-xeon|5|16|32|128|Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz|Group Valenti
... ... @@ -29,11 +29,14 @@
29 29  |barcelona|8|40|320|192|Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz|(((
30 30  Group Valenti
31 31  )))
32 -|barcelona|1|40|40|512| |Group Valenti
28 +|barcelona|1|40|40|512|(((
29 +Intel(R) Xeon(R) Silver 4316 CPU @ 2.30GHz
30 +)))|Group Valenti
33 33  |mallorca|4|48|192|256|AMD EPYC 7352 24-Core Processor|Group Valenti
34 -|calea|36|64|2304|256|Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz|(((
35 -Group Rezzolla
32 +|calea|36|64|2304|512|Intel(R) Xeon(R) Platinum 8358 CPU @ 2.10GHz|(((
33 +Group Valenti
36 36  )))
35 +|bilbao|7|64|448|256|Intel Xeon(R) Gold 6540 @ 2.20GHz
37 37  |majortom|1|64|64|256|AMD EPYC 7513 32-Core Processor|Group Bleicher
38 38  
39 39  Most nodes are for exclusive use by their corresponding owners. The itp nodes are for common usage. Except for 'fplo' and 'dfg-big' nodes, all machines are connected with Infiniband for all traffic (IP and internode communitcation - MPI)
... ... @@ -59,13 +59,8 @@
59 59  You don't have to worry about the number of processes or specific nodes. Both slurm and openmpi know
60 60  about each other.
61 61  
62 -If you want **infiniband** for your MPI job (which is usually a good idea, if not running on the same node), you have to request the feature infiniband:
63 -
64 -{{{ sbatch -p dfg -C infiniband -n X jobscript.sh}}}
65 -
66 -Note: Infiniband is not available for 'fplo' and 'dfg-big'.
67 -
68 68  Running **SMP jobs** (multiple threads, not necessary mpi). Running MPI jobs on a single node is recommended for the
62 +
69 69  dfg-big nodes. This are big host with up to 64 cpu's per node, but 'slow' gigabit network connection. Launch SMP jobs with
70 70  
71 71  {{{ sbatch -p PARTITION -N 1 -n X jobscript.sh}}}
... ... @@ -84,7 +84,7 @@
84 84  
85 85  where <MB> is the memory in megabytes. The virtual memory limit is 2.5 times of the requested real memory limit.
86 86  
87 -The memory limit is not a hard limit. When exceeding the limit, your memory will be swapped out. Only when using more the 150% of the limit your job will be killed. So be conservative, to keep enough room for other jobs. Requested memory is blocked from the use by other jobs.
81 +The memory limit is not a hard limit. When exceeding the limit, your memory will be swapped out. Only when using more the 110% of the limit your job will be killed. So be conservative, to keep enough room for other jobs. Requested memory is blocked from the use by other jobs.
88 88  
89 89  {{{ -t or --time=<time>}}}
90 90