Deploying RMACC summit: An HPC resource for the rocky mountain region

  • Jonathon Anderson
  • , Patrick J. Burns
  • , Daniel Milroy
  • , Peter Ruprecht
  • , Thomas Hauser
  • , Howard Jay Siegel

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

57 Scopus citations

Abstract

RMACC Summit is a heterogeneous supercomputer cluster with an aggregate floating point performance of 379 TFLOPS (Rmax, as currently configured) that provides about 85 million core-hours/year to researchers from institutions participating in the Rocky Mountain Advanced Computing Consortium (RMACC) . The development of Summit was a collaborative effort toward specifying a system that meets the needs of researchers at multiple universities, and included implementation and testing of several new technologies. We discuss our experiences in creating and maintaining a successful ongoing collaboration between the two universities that are RMACC Summit's primary operators, and consider both the technical and support challenges of extending that collaboration to other regional users.

Original languageEnglish
Title of host publicationPEARC 2017 - Practice and Experience in Advanced Research Computing 2017
Subtitle of host publicationSustainability, Success and Impact
PublisherAssociation for Computing Machinery
ISBN (Electronic)9781450352727
DOIs
StatePublished - Jul 9 2017
Externally publishedYes
Event2017 Practice and Experience in Advanced Research Computing, PEARC 2017 - New Orleans, United States
Duration: Jul 9 2017Jul 13 2017

Publication series

NameACM International Conference Proceeding Series
VolumePart F128771

Conference

Conference2017 Practice and Experience in Advanced Research Computing, PEARC 2017
Country/TerritoryUnited States
CityNew Orleans
Period07/9/1707/13/17

Keywords

  • Clusters
  • High-Performance Computing
  • Supercomputers

Fingerprint

Dive into the research topics of 'Deploying RMACC summit: An HPC resource for the rocky mountain region'. Together they form a unique fingerprint.

Cite this