2016 IEEE International Parallel and Distributed Processing Symposium Workshops (IPDPSW) 2016
DOI: 10.1109/ipdpsw.2016.81
|View full text |Cite
|
Sign up to set email alerts
|

Systemwide Power Management with Argo

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
4
0

Year Published

2016
2016
2020
2020

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 13 publications
(4 citation statements)
references
References 17 publications
0
4
0
Order By: Relevance
“…We can outline the fact that a programming paradigm based on a graph of parallel and distributed tasks can obtain better performances on a huge amount of cores. Future supercomputers and post-petascale platforms would propose middle-ware and systems with smarter schedulers [12] and dedicated I/O systems [14] which will allow some efficient data persistence and anticipation of data migrations. In those machines, programming paradigms such as YML/XMP would be well-adapted and efficient.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…We can outline the fact that a programming paradigm based on a graph of parallel and distributed tasks can obtain better performances on a huge amount of cores. Future supercomputers and post-petascale platforms would propose middle-ware and systems with smarter schedulers [12] and dedicated I/O systems [14] which will allow some efficient data persistence and anticipation of data migrations. In those machines, programming paradigms such as YML/XMP would be well-adapted and efficient.…”
Section: Discussionmentioning
confidence: 99%
“…Condor and PaRSEC are middlewares created for Grid then adapted to super-computers but they don't provide all the functionalities the next generation of supercomputer will need. Argo [12] is an operating system for extreme scale computing. It allows to reconfigure the resource nodes dynamically depending on a workload, to support massive concurrency, to present a hierarchical framework for power and fault management and a communication infrastructure.…”
Section: Related Workmentioning
confidence: 99%
“…Summarizing many of the available options, [31] discussed interactions between controls at different levels (server, rack, group of racks) with different objectives (energy efficiency, capping, performance) and actuators (p-states, turning machines off, admission control, power budget management). We also note [32] as an example of recent power management work for supercomputers.…”
Section: Related Workmentioning
confidence: 99%
“…Again, this work can be done at the processor-level [23,24,44,56], DRAM [11], storage [30], and across a data-center [33,39]. At the data-center or cluster-level, power can be saved by consolidating workloads to use fewer physical machines [14,27,34,35,37,54], coordinating co-existing applications [45], and scheduling with green power [20] Scheduling jobs under a power cap has recently become a major concern for HPC operating systems [7,15] and job schedulers [3,19]. Recent work suggests that HPC workloads can actually achieve higher performance by over-provisioning large-scale installationssuch that using all nodes at full capacity would drastically violate the power budget-and severely power capping the individual nodes [47].…”
Section: Related Workmentioning
confidence: 99%