Niagara

From CC Doc
(Redirected from LP)
Jump to: navigation, search
Other languages:
English • ‎français
Expected availability: April 2018
Login node: niagara.computecanada.ca
GlobusGlobus is a file transfer service [https://www.globus.org/] endpoint: computecanada#niagara
Data mover nodes (rsync, scp, ...): nia-dm2, nia-dm2, see Moving data
System Status Page: https://docs.scinet.utoronto.ca

Niagara is a homogeneous cluster, owned by the University of Toronto and operated by SciNet, intended to enable large parallel jobs of 1040 cores and more. It was designed to optimize throughput of a range of scientific codes running at scale, energy efficiency, and network and storage performance and capacity.

The Niagara Quickstart has specific instructions for Niagara, where the user experience on Niagara is similar to that on Graham and Cedar, but slightly different.

Niagara is an allocatable resource in the 2018 Resource Allocation Competition (RAC 2018), which has come into effect on April 4, 2018.

Niagara installation update at the SciNet User Group Meeting on February 14th, 2018

Niagara installation time-lag video


Niagara hardware specifications

  • 1500 nodes, each with 40 Intel Skylake cores at 2.4GHz, for a total of 60,000 cores.
  • 202 GB (188 GiB) of RAM per node.
  • EDR Infiniband network in a so-called 'Dragonfly+' topology.
  • 6PB of scratch, 3PB of project space (parallel filesystem: IBM Spectrum Scale, formerly known as GPFS).
  • 256 TB burst buffer (Excelero + IBM Spectrum Scale).
  • No local disks.
  • No GPUs.
  • Rpeak of 4.61 PF.
  • Rmax of 3.0 PF.
  • 685 kW power consumption.

Attached storage systems

Home space
200TB total volume
Parallel high-performance filesystem (IBM Spectrum Scale)
  • Location of home directories.
  • Available as the $HOME environment variable.
  • Each home directory has a small, fixed quota of 100GB.
  • Not allocated, standard amount for each user. For larger storage requirements, use scratch or project.
  • Has daily backup.
Scratch space
7PB total volume
Parallel high-performance filesystem (IBM Spectrum Scale)
  • For active or temporary (/scratch) storage (~ 80 GB/s).
  • Available as the $SCRATCH environment variable.
  • Not allocated.
  • Large fixed quota per user and per group path.
  • Inactive data will be purged.
Burst buffer
256TB total volume
Parallel extra high-performance filesystem (Excelero+IBM Spectrum Scale)
  • For active fast storage during a job (160GB/s, and very high IOPS).
  • Not fully configured yet, but data will be purged very frequently (i.e. soon after a job has ended) and space on this storage tier will not be RAC allocatable.
Project space
2PB total volume.
Parallel high-performance filesystem (IBM Spectrum Scale
  • Allocated via RAC.
  • For active but low data turnover storage and relatively fixed datasets
  • Available as the $PROJECT environment variable.
  • quota set per project path.
  • Backed up.
Archive Space
10PB total volume
High Performance Storage System (IBM HPSS)
  • Allocated via RAC.
  • Nearline accessible space intended for large datasets requiring offload from active filesystems.
  • Available as the $ARCHIVE environment variable.
  • Large fixed quota per group.
  • Tape based backend (dual copy).

High-performance interconnect

The Niagara cluster has an EDR Infiniband network in a so-called 'Dragonfly+' topology, with four wings. Each wing of maximually 432 nodes (i.e., 17280) has 1-to-1 connections. Network traffic between wings is done through adaptive routing, which alleviates network congestion and yields an effective blocking of 2:1 between nodes of different wings.

Node characteristics

  • CPU: 2 sockets with 20 Intel Skylake cores (2.4GHz, AVX512), for a total of 40 cores per node
  • Computational performance: 3 TFlops theoretical peak.
  • Network connection: 100Gb/s EDR Dragonfly+
  • Memory: 202 GB (188 GiB) of RAM, i.e., a bit over 4GiB per core.
  • Local disk: none. GPUs/Accelerators: none.
  • Operating system: Linux CentOS 7

Scheduling

The Niagara cluster uses the Slurm scheduler to run jobs. The basic scheduling commands are therefore similar to those for Cedar and Graham, with a few differences:

  • Scheduling is by node only. This means jobs always need to use multiples of 40 cores per job.
  • Asking for specific amounts of memory is not be necessary and is discouraged; all nodes have the same amount of memory (202GB/188GiB minus some operating system overhead).

Details, such as how to request burst buffer usage in jobs, are still being worked out.

Software

  • Module-based software stack.
  • Both the standard Compute Canada software stack as well as cluster-specific software tuned for Niagara are available.
  • In contrast with Cedar and Graham, no modules are loaded by default to prevent accidental conflicts in versions. To load the software stack that a user would see on Graham and Cedar, one can load the "CCEnv" module (see Niagara Quickstart).

Access and Migration to Niagara

Migration for Existing Users of SciNet Systems

  • Accounts, $HOME & $PROJECT of active GPC users have been transferred to Niagara (except dot-files in ~).
  • Data stored in $SCRATCH has not been, and will not be, transfered automatically.
  • Users are to clean up $SCRATCH on the GPC as much as possible (remember it's temporary data!). Then they can transfer what they need using datamover nodes. Let us know if you need help.
  • To enable this transfer, there will be a short period during which you can have access to Niagara as well as to the GPC storage resources. This period will end no later than May 9, 2018.

New Users (without a previous SciNet account)

  • Those of you new to SciNet, but with 2018 RAC allocations on Niagara, have had your accounts created and ready for you to login.

  • New, non-RAC users: we are still working out the procedure to get access. If you can't wait, for now, you can follow the old route of requesting a SciNet Consortium Account on the CCDB site, or write to support@scinet.utoronto.ca.

Getting started

See Niagara Quickstart.