CHPC Computational Hardware

Updraft Cluster

Updraft Cluster Hardware Overview

  • Capability Cluster for Large Parallel Jobs
  • 256 Dual-Quad Core Nodes (2048 total cores)
  • 2.8 GHz Intel Xeon (Harpertown) processors
  • 16 Gbytes memory per node (2 Gbytes per processor core)
  • Qlogic Infiniband DDR (InfiniPath QLE 7240) interconnect
  • Gigabit Ethernet interconnect

NFS Home Directory

NFS mounted file system, your home directory is one choice for i/o. Speed wise this space carries the worst statistical performance. This space is visible to all of the nodes of the clusters through an auto-mounting system.

NFS Scratch (/scratch/general, /scratch/uintah)

NFS mounted file system There are two NFS scratch filesystems for use on uintah, depending upon your group. If you aren't sure which space to use, it is probably the /scratch/general space. The uintah space is reserved for the users of the uintah allocation and nodes.

This space is visible to all arches nodes and can be access with the path /scratch/general or /scratch/uintah. Each user will be responsible for creating directories and cleaning up after their jobs. This filesystem is not backed up.

Local Disk (/tmp)

Local Scratch space is the storage space unique to each individual node. Local Scratch is cleaned aggressively and is not supported by CHPC. It can be accessed on each node through "/tmp". This space will be the fastest, but not necessarily the largest. Users should use this space at their own risk.

When running jobs, it is important to know that making a flow from one storage system to another is the best idea. For example, taking a job that isn't too large and doesn't need much time on the node should be placed in the "/scratch/general" and then outputted to the user's home directory using a batch job.

It is also important to keep in mind that ALL users must remove excess files on their own. Preferably this can be done with the user's batch job when he/she has finished the computation. Leaving files in any "/scratch/" space creates an impediment to other users who are trying to run their own jobs. Simply delete all extra files from any space other than your home directory when it is not being used immediately.

Arches Clusters

sanddunearch (156 nodes, 312 procs, 624 cores)

  • "parallel cluster" for highly parallel parallel jobs requiring high speed interconnect.
  • 2.4 GHz dual-core Opteron processors
  • 8 Gbytes memory per node (2 Gbytes per processor core)
  • Both Infiniband and Gigabit Ethernet interconnects
  • 156 nodes available to the general pool
  • Some restricted nodes:
sanddunearch restricted nodes
Research Group proc speed node memory node/procs fast interconnect
Molinero 2.6 GHz 8 Gbytes 24/96 infiniband
Schuster 1.8 GHz 2 Gbytes 12/48 infiniband

delicatearch (256 nodes, 512 procs)

  • "parallel cluster" for highly parallel parallel jobs requiring high speed interconnect.
  • 1.4 GHz Opteron processors
  • 2 Gbytes memory per node
  • Both Myrinet and Gigabit Ethernet interconnects

tunnelarch (48 nodes, 96 procs)

  • "data mining cluster" for jobs requiring large memory.
  • 1.4 and 1.8 GHz Opteron processors
  • 4 Gbytes memory per node
  • Gigabit Ethernet interconnect

marchingmen (164 nodes, 328 procs)

  • "cycle farm" for serial and smaller parallel
  • jobs which do not require a high speed interconnect.
  • 1.4 and 1.8 GHz Opteron processors
  • 2 Gbytes memory per node
  • Gigabit Ethernet interconnect

landscapearch (restricted)

  • Limited availability
landscapearch restricted nodes
Research Group proc speed node memory node/procs fast interconnect
Voth 1.4 GHz 2 Gbytes 16/32 no
2.2 GHz 4 Gbytes 14/28 no
2.6 GHz 4 Gbytes 51/102 myrinet
Violi 1.4 GHz 4 Gbytes 9/18 myrinet
Schuster 1.8 GHz 2 Gbytes 64/128 myrinet
Zhdanov 1.8 GHz 4 Gbytes 4/8 no
Simons 2.0 GHz 8 Gbytes 6/24 no
Horel/Steenburgh 2.2 GHz 8 Gbytes 1/4 no
Liu 2.2 GHz 8 Gbytes 6/24 no
Reichler 2.2 GHz 8 Gbytes 4/16 no
CHPC* 2.4 GHz 32 Gbytes 1/4 no

Telluride Cluster

Telluride Cluster Overview (restricted)

  • For dedicated use by one research group
  • 72 nodes, 576 processors
  • 2.333 (48 nodes) and 2.66 (24 nodes) GHz processors
  • 16 Gbytes memory per node
  • Inifiniband interconnect