CPU Nodes
The IBEX cluster contains different architectures of CPUs like Skylakes, Haswell, Ivy Bridge, Sandy Bridge, Westmere and AbuDhabi .
These different CPUs are accessed (for your source code compilation and job submission) using the following login nodes:
- All Intel CPU nodes : ilogin.ibex.kaust.edu.sa
- Intel Skylake CPU nodes only: slogin.ibex.kaust.edu.sa
- AMD nodes: alogin.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 amd}" or by directly specifying the CPU type as shown below .
For example, “--constraint=cpu_intel_gold_6148” is for Skylake CPUs.
Table 1. Ibex CPU Resources
|
CPU Family |
CPU |
Nodes |
CORES |
CLOCK |
FLOPS |
GFLOPS |
Tflops |
|
Skylake |
cpu_intel_gold_6148 |
106 |
40 |
2.60 |
32 |
352768 |
397.82 |
|
cpu_intel_gold_6142 |
8 |
32 |
2.60 |
32 |
21299 |
||
|
cpu_intel_gold_6142 |
4 |
32 |
2.60 |
32 |
10650 |
||
|
cpu_intel_xeon_gold_6134m |
4 |
32 |
3.20 |
32 |
13107 |
||
|
|
|
|
|
|
|
|
157.18 |
|
Haswell |
cpu_intel_e5_2699_v3 |
16 |
36 |
2.30 |
16 |
21197 |
|
|
|
|
|
|
|
|
|
|
|
Ivy Bridge |
cpu_intel_e5_2680_v2 |
144 |
20 |
2.80 |
8 |
64512 |
|
|
cpu_intel_e5_2670_v2 |
32 |
20 |
2.50 |
8 |
13200 |
||
|
|
|
|
|
|
|
|
|
|
Sandy Bridge |
cpu_intel_e5_2670 |
100 |
16 |
2.60 |
8 |
33946 |
|
|
|
|
|
|
|
|
|
|
|
Westmere |
cpu_intel_e7_2830 |
2 |
64 |
2.13 |
4 |
1091 |
|
|
cpu_intel_e7_2860 |
2 |
80 |
2.26 |
4 |
1446 |
||
|
|
|
|
|
|
|
|
|
|
Abu Dhabi |
cpu_amd_6376 |
24 |
64 |
2.30 |
4 |
14131 |
|
|
cpu_amd_6376 (lm) |
13 |
64 |
2.30 |
4 |
7654 |
||
|
Total (theoretical) |
555 |
||||||
When submitting a job, user is able to select the desired resources by precising contraints. For example,
sbatch --constraint=intel my_job.sh
runs the job on Intel nodes only.
sbatch --constaint=amd my_job.sh
runs the job on AMD 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.