Case Study on Co-scheduling for HPC Applications

Jens Breitbart, Josef Weidendorfer, Carsten Trinitis

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

20 Scopus citations

Abstract

Most applications running on supercomputers achieve only a fraction of the peak performance of the system. In this paper we analyze the performance and energy efficiency of co-scheduling one memory bandwidth bound and one compute bound application on the same node. We present auto pin+, a tool designed to monitor and optimize co-scheduling of applications. Our analysis shows that co-scheduling can improve both energy efficiency and overall throughput of a supercomputer. At best, runtime can be decreased by 28% and the energy consumption by 12%, respectively, compared to best case dedicated execution. The overall efficiency however strongly depends on the ratio of jobs available in the queue. We furthermore present a simple adaptive strategy depending on the available jobs in the queue.

Original languageEnglish
Title of host publicationProceedings - 2015 International Conference on Parallel Processing Workshops, The 44th Annual Conference, ICPPW 2015
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages277-285
Number of pages9
ISBN (Electronic)9781467375894
DOIs
StatePublished - 8 Dec 2015
Event44th Annual Conference of the International Conference on Parallel Processing Workshops, ICPPW 2015 - Beijing, China
Duration: 1 Sep 20154 Sep 2015

Publication series

NameProceedings of the International Conference on Parallel Processing Workshops
Volume2015-January
ISSN (Print)1530-2016

Conference

Conference44th Annual Conference of the International Conference on Parallel Processing Workshops, ICPPW 2015
Country/TerritoryChina
CityBeijing
Period1/09/154/09/15

Keywords

  • Co-scheduling
  • Energy efficiency
  • HPC
  • Job scheduling

Fingerprint

Dive into the research topics of 'Case Study on Co-scheduling for HPC Applications'. Together they form a unique fingerprint.

Cite this