Proceedings of the ACM Symposium on Cloud Computing 2018
DOI: 10.1145/3267809.3267819
|View full text |Cite
|
Sign up to set email alerts
|

Stratus

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
6
3

Relationship

0
9

Authors

Journals

citations
Cited by 64 publications
(9 citation statements)
references
References 33 publications
0
9
0
Order By: Relevance
“…To overcome such limitations, some solutions jointly process batches of tasks. For instance, Stratus [29] proposes an algorithm that targets the IaaS (Infrastructure as a Service) scenario; specifically, it aims to maximize the use of the purchased resources by co-allocating tasks onto the same VMs. Quincy [30] introduces the concept of flow scheduling, where the problem of job scheduling is converted to an equivalent min-cost max-flow problem.…”
Section: Related Workmentioning
confidence: 99%
“…To overcome such limitations, some solutions jointly process batches of tasks. For instance, Stratus [29] proposes an algorithm that targets the IaaS (Infrastructure as a Service) scenario; specifically, it aims to maximize the use of the purchased resources by co-allocating tasks onto the same VMs. Quincy [30] introduces the concept of flow scheduling, where the problem of job scheduling is converted to an equivalent min-cost max-flow problem.…”
Section: Related Workmentioning
confidence: 99%
“…To reduce the service cost, Chung et al [22] introduced Stratus, which was used to pack the tasks on the machines using the estimated runtime for the incoming jobs. The JVuPredict [23] algorithm was used to predict the estimated runtime of the tasks.…”
Section: Literature Reviewmentioning
confidence: 99%
“…The key design is to leverage lightweight virtualization, a.k.a, containers to make tasks preemptable in cluster scheduling. Stratus 47 proposes a cost‐aware container scheduler, which orchestrates batch job execution on virtual clusters, dynamically allocated collections of virtual machine instances. To our best knowledge, the preemption performance in current preemptive schedulers such as References 42,46,48,49 is limited and most cloud deadline schedulers rarely consider preemption.…”
Section: Related Workmentioning
confidence: 99%