Table of Contents |
---|
Overview
Phoenix is a heterogeneous supercomputer. Heterogeneous supercomputers feature processors and interconnects that are of different types, brands, and architectures. This can complicate system management and optimization but offers a wider range of available hardware. This page describes the publicly available hardware within Phoenix for reference
...
Info |
---|
There is privately owned hardware that has very different specs. See the Phx Status Page for the full features of every node |
Requesting Resources
Excerpt | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Requesting CPUsTo request a given number of CPUs sharing the same node, you can use the following in your
This will create a job with 5 CPU cores on one node. To request a given number of CPUs spread across multiple nodes, you can use the following:
The above example will allocate a total of 50 cores spread across as few as 2 nodes or as many as 4 nodes. Take note of the inclusion or omission of
This reduced example will still allocate 50 cores, 5 cores per task on any number of available nodes. Note, that unless you are using MPI-aware software, you will likely prefer to always add The See the official Slurm documentation for more information: https://slurm.schedmd.com/sbatch.html Requesting MemoryCores and memory are de-coupled: if you need only a single CPU core but ample memory, you can do so like this:
If you do not specify To request more than 512GiB of memory, you will need to use the highmem partition
To request all available memory on a node:
Requesting GPUsTo request a GPU, you can specify the This will allocate the first available GPU that fits your job request
To request multiple GPU’s specify a number greater than 1:
To request a specific number of GPU’s per node when running multi node:
To request a specific type of GPU (a100 for example):
|
CPU Micro-Architectures
The Phoenix cluster includes CPUs of different micro-architectures, such as Cascade Lake and Broadwell. These micro-architectures represent different generations of Intel processors, with variations in performance, instruction sets, and optimization capabilities. Software may perform differently depending on the CPU architecture it was compiled for or is optimized to run on.
To specify a particular CPU architecture for your job, use the --constraint
flag (-C
).
For example, to request a cascadelake CPU,
Code Block |
---|
#SBATCH -C cascadelake
or
interactive -C cascadelake |
To request any ‘newer’ CPU that supports the AVX512 instruction set,
Code Block |
---|
#SBATCH -C avx512
or
interactive -C avx512 |
Additional Help
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|