SC16: International Conference for High Performance Computing, Networking, Storage and Analysis 2016
DOI: 10.1109/sc.2016.84
|View full text |Cite
|
Sign up to set email alerts
|

Transient Guarantees: Maximizing the Value of Idle Cloud Capacity

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 19 publications
(5 citation statements)
references
References 14 publications
0
5
0
Order By: Relevance
“…While this change reduced some of the complexity of using spot VMs and much of their demand-induced volatility, it also eliminated many of their benefits. By not setting the price based on supply and demand, users have less visibility into when their VMs may be revoked, i.e., they could be revoked when the price is above or below their maximum price, which makes it difficult to optimally configure applications to minimize the performance impact of revocations [27]. In addition, users cannot necessarily obtain spot VMs at any time under periods of resource constraint if they are willing to pay a high enough price, i.e., by forcing EC2 to revoke VMs from a lower-paying user.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…While this change reduced some of the complexity of using spot VMs and much of their demand-induced volatility, it also eliminated many of their benefits. By not setting the price based on supply and demand, users have less visibility into when their VMs may be revoked, i.e., they could be revoked when the price is above or below their maximum price, which makes it difficult to optimally configure applications to minimize the performance impact of revocations [27]. In addition, users cannot necessarily obtain spot VMs at any time under periods of resource constraint if they are willing to pay a high enough price, i.e., by forcing EC2 to revoke VMs from a lower-paying user.…”
Section: Discussionmentioning
confidence: 99%
“…For example, to enable accessibility for a high enough price, EC2 must be willing to revoke spot VMs from their current users and provision them to users willing to pay more. Such revocations, which are akin to failures, incur an overhead that reduces the performance capacity (and thus value) of spot VMs [27,32]. Many applications also either fail or perform poorly under unexpected and frequent revocations, and require significant modifications to gracefully handle them.…”
Section: Background and Motivationmentioning
confidence: 99%
“…AWS allows customers to bid on spot instances while Azure and Google Cloud [29,34] sell them at globally fixed prices. Prior research has explored the economic incentives for spot instances [41,42,50,64,67,100,102,108,110,112,113]. However, prior work used full spot instances to produce memory; Memtrade is more generic, enabling finegrained consumption of excess memory from any instance type.…”
Section: Related Workmentioning
confidence: 99%
“…Dynamic pricing is an efective mechanism to stabilize demands for networking, computing, and utility resources [28,52,53]. Auction-based pricing [55,76] has been introduced in IaaS cloud markets to encourage SPs' consuming spare resources, where they bid against dynamically-set cheaper spot prices with no or little availability guarantees, e.g., Amazon EC2's spot instances [4,42].…”
Section: Related Workmentioning
confidence: 99%