2012
DOI: 10.1016/j.jpdc.2012.02.014
|View full text |Cite
|
Sign up to set email alerts
|

Dual time-scale distributed capacity allocation and load redirect algorithms for cloud systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
70
0

Year Published

2013
2013
2021
2021

Publication Types

Select...
4
4
1

Relationship

4
5

Authors

Journals

citations
Cited by 76 publications
(78 citation statements)
references
References 24 publications
0
70
0
Order By: Relevance
“…Scheduling is often assumed to be first-come first-served (FCFS) or processor sharing (PS). In particular, the M/G/1 PS queue is a common abstraction used to model a CPU and it has been adopted in many cloud studies [47,48], thanks to its simplicity and the suitability to apply the model to multi-class workloads. For instance, an SLA-aware capacity allocation mechanism for cloud applications is derived in [47] using an M/G/1 PS queue as the QoS model.…”
Section: Performance Modelsmentioning
confidence: 99%
“…Scheduling is often assumed to be first-come first-served (FCFS) or processor sharing (PS). In particular, the M/G/1 PS queue is a common abstraction used to model a CPU and it has been adopted in many cloud studies [47,48], thanks to its simplicity and the suitability to apply the model to multi-class workloads. For instance, an SLA-aware capacity allocation mechanism for cloud applications is derived in [47] using an M/G/1 PS queue as the QoS model.…”
Section: Performance Modelsmentioning
confidence: 99%
“…Hence, the SaaS faces the problem of determining every hour the optimal number of VMs for each WS class in order to minimize costs and penalties. Resource allocation is performed on the basis of a prediction of future WS workloads (Ardagna et al 2012a, Zhu et al 2009b) and we will denote with Λ k the prediciton of the arrival rate for WS application k for the next time horizon. The SaaS needs also an estimate of the future performance of each VM in order to determine application average response time.…”
Section: Problem Statementmentioning
confidence: 99%
“…If reserved resources are not sufficient (step 3d), reserved instances are rescaled and the number of desired on spot instances is computed (step 3e). As in (Ardagna et al 2012a, Zhu et al 2009a), we set U = 0.6.…”
Section: Equilibria Efficiencymentioning
confidence: 99%
“…This is especially necessary when the load balancer also acts as a resource allocator deciding not only where to route the current request but also how much resources it would have to execute, like in [3]. In these cases, the induced sudden lack of resources can result in poor performance.…”
Section: Related Workmentioning
confidence: 99%