CPU Nodes
The IBEX cluster contains different architectures of CPUs like CascadeLakes, Skylakes, Ivy Bridge and Sandy Bridge.
These different CPUs are accessed (for your source code compilation and job submission) using the following login node:
- ilogin.ibex.kaust.edu.sa
The IBEX cluster CPU compute nodes are summarized in Table 1. These various CPUs are accessed by the SLURM scheduling using the constraint "#SBATCH --constraint=intel" or by directly specifying the CPU type as shown below .
For example, “--constraint=cpu_intel_gold_6148” is for Skylake CPUs or just "--constraint=skylake”.
Table 1. Ibex CPU Resources
|
CPU Family |
CPU |
Nodes |
CORES |
CLOCK |
FLOPS |
||
|
Skylake |
cpu_intel_gold_6148 |
108 |
40 |
2.60 |
32 |
||
|
Ivy Bridge |
cpu_intel_e5_2680_v2 |
144 |
20 |
2.80 |
8 |
||
|
cpu_intel_e5_2670_v2 |
30 |
20 |
2.50 |
8 |
|||
|
Sandy Bridge |
cpu_intel_e5_2670 |
96 |
16 |
2.60 |
8 |
||
|
Cascadelake |
cpu_intel_gold_6248 |
106 |
40 |
2.50 |
32 |
When submitting a job, the user is able to select the desired resources with precise constraints. For example,
sbatch --constraint=intel my_job.sh
runs the job on Intel nodes only.
sbatch --constaint=cascadelake my_job.sh
runs the job on Cascadelake nodes only.
sbatch --constraint=[intel]&[local_1T] my_job.sh
runs the jobs only on Intel node, having at least a local disk of 1 TB along.