2011 IEEE International Conference on Cluster Computing 2011
DOI: 10.1109/cluster.2011.56
|View full text |Cite
|
Sign up to set email alerts
|

An RMS for Non-predictably Evolving Applications

Abstract: Non-predictably evolving applications are applications that change their resource requirements during execution. These applications exist, for example, as a result of using adaptive numeric methods, such as adaptive mesh refinement and adaptive particle methods. Increasing interest is being shown to have such applications acquire resources on the fly. However, current HPC Resource Management Systems (RMSs) only allow a static allocation of resources, which cannot be changed after it started. Therefore, non-pre… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2013
2013
2023
2023

Publication Types

Select...
3
2
2

Relationship

1
6

Authors

Journals

citations
Cited by 8 publications
(4 citation statements)
references
References 20 publications
0
4
0
Order By: Relevance
“…Moldable or malleable applications [17] can be directed to trade resources for execution time, for example, an application may run on 4 cores for 1 hour or 2 cores for 2 hours. This additional flexibility in resource management has been shown to bring significant gains [25,27,44,47]. However, the amount of computations essentially remains the same.…”
Section: Application Vs Infrastructure Centricmentioning
confidence: 98%
“…Moldable or malleable applications [17] can be directed to trade resources for execution time, for example, an application may run on 4 cores for 1 hour or 2 cores for 2 hours. This additional flexibility in resource management has been shown to bring significant gains [25,27,44,47]. However, the amount of computations essentially remains the same.…”
Section: Application Vs Infrastructure Centricmentioning
confidence: 98%
“…In the context of cloud computing, some solutions for elasticity in I/O have been proposed, such as SpringFS ( Xu et al, 2014 ) as well as solutions based on the Hadoop Distributed File System (HDFS) ( Lim et al, 2010;Cheng et al, 2012 ). Nonetheless, by and large, existing malleability solutions ( Casanova et al, 2014;Kalé et al, 2002;Klein and Pérez, 2011;Hungershofer, 2004;Cirne and Berman, 2002;Prabhakaran et al, 2015 ) are mostly confined to the elasticity of compute and memory allocations.…”
Section: I/o-aware Coordination and Modellingmentioning
confidence: 99%
“…every hours by picking an amount to add/delete randomly. The second one is called AMR, it uses the elasticity model introduced in [35].…”
Section: A Scenariomentioning
confidence: 99%