Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
(Usable memory changed to preferred Slurm usage) |
(reformat hardware table) |
||
Line 66: | Line 66: | ||
<!--T:17--> | <!--T:17--> | ||
Cedar has a total of 58,416 CPU cores for computation, and 584 GPU devices. Total theoretical peak double precision performance is 936 teraflops for CPUs, plus 2,744 for GPUs, yielding over 3.6 petaflops of theoretical peak double precision performance. 22 fully connected "islands" of 32 base or large nodes each have 1024 cores in a fully non-blocking topology (Omni-Path fabric), with each island designed to yield over 30 teraflops of double-precision performance (measured with high performance LINPACK). There is a 2:1 blocking factor between the 1024 core islands. | Cedar has a total of 58,416 CPU cores for computation, and 584 GPU devices. Total theoretical peak double precision performance is 936 teraflops for CPUs, plus 2,744 for GPUs, yielding over 3.6 petaflops of theoretical peak double precision performance. 22 fully connected "islands" of 32 base or large nodes each have 1024 cores in a fully non-blocking topology (Omni-Path fabric), with each island designed to yield over 30 teraflops of double-precision performance (measured with high performance LINPACK). There is a 2:1 blocking factor between the 1024 core islands. | ||
<!--T:7--> | <!--T:7--> | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
! Count !! Node type !! Cores !! Available memory !! Hardware detail | |||
|- | |- | ||
| base | | 576 || base "128G" || 32 || 125G or 128000M || two Intel E5-2683 v4 "Broadwell" at 2.1Ghz | ||
|- | |- | ||
| large | | 128 || large "256G" || 32 || 250G or 257000M || (same as base nodes) | ||
|- | |- | ||
| | | 24 || large "512G" || 32 || 502G or 515000M || (same as base nodes) | ||
|- | |- | ||
| | | 24 ||bigmem1500 "1.5T"|| 32 || 1510G or 1547000M || (same as base nodes) | ||
|- | |- | ||
| | | 4 || bigmem3000 "3T" || 64 || 3022G or 3095000M || four Intel E7-4809 v4 "Broadwell" at 2.1Ghz | ||
|- | |- | ||
| | | 114 || base GPU || 24 || 125G or 128000M || two E5-2650 v4 at 2.2GHz + four NVIDIA P100 Pascal GPUs (12GB HBM2 memory) | ||
|- | |- | ||
| | | 32 || large GPU || 24 || 250G or 257000M || two E5-2650 v4 at 2.2GHz + four NVIDIA P100 Pascal GPUs (16GB HBM2 memory) | ||
|- | |- | ||
| Skylake | | 640 || Skylake || 48 || 187G or 192000M || two Intel Platinum 8160F "Skylake" at 2.1Ghz | ||
|} | |} | ||
Note that the amount of available memory is less than the "round number" suggested by the hardware configuration. For instance, "base" nodes do have 128 GiB of RAM, but some of it is permanently occupied by the kernel and OS. To avoid wasting time by swapping/paging, the scheduler will never allocate jobs whose memory requirements exceed the amount of "available" memory shown above. | |||
<!--T:10--> | <!--T:10--> | ||
All | All nodes have local (on-node) temporary storage. GPU nodes have a single 800GB SSD drive. All other compute nodes have two 480GB SSD drives, for a total raw capacity of 960GB. Best practice to access node-local storage is to use the directory generated by [[Running jobs|Slurm]], $SLURM_TMPDIR. | ||
<!--T:18--> | <!--T:18--> |