The platform will undergo maintenance on Sep 14 at about 7:45 AM EST and will be unavailable for approximately 2 hours.
2016
DOI: 10.48550/arxiv.1602.01412
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Canary: A Scheduling Architecture for High Performance Cloud Computing

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

2016
2016
2019
2019

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(9 citation statements)
references
References 22 publications
0
9
0
Order By: Relevance
“…With empty tasks [28], the resulting upper bound on task scheduling throughput fails to represent useful work within a realistic application. With non-empty tasks, since the efficiency of the overall application is typically not reported [3,6], TPS is not a measurement of runtime-limited performance. Large tasks may be used to hide any amount of runtime overhead, while small tasks may result in a drop in total application throughput even as TPS increases.…”
Section: Metgmentioning
confidence: 99%
See 2 more Smart Citations
“…With empty tasks [28], the resulting upper bound on task scheduling throughput fails to represent useful work within a realistic application. With non-empty tasks, since the efficiency of the overall application is typically not reported [3,6], TPS is not a measurement of runtime-limited performance. Large tasks may be used to hide any amount of runtime overhead, while small tasks may result in a drop in total application throughput even as TPS increases.…”
Section: Metgmentioning
confidence: 99%
“…Limit studies of task scheduling throughput in various runtime systems often make additional assumptions. A popular assumption is the use of trivially parallel tasks [3,6], which as shown in Section 5.5 underestimates (often substantially) the cost of scheduling a task and can also impact scalability.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Most cluster computing frameworks, such as Spark [64], CIEL [40], and Dryad [28] implement a centralized scheduler, which can provide locality but at latencies in the tens of ms. Distributed schedulers such as work stealing [12], Sparrow [45] and Canary [47] can achieve high scale, but they either don't consider data locality [12], or assume tasks belong to independent jobs [45], or assume the computation graph is known [47].…”
Section: Bottom-up Distributed Schedulermentioning
confidence: 99%
“…Canary [47] achieves impressive performance by having each scheduler instance handle a portion of the task graph, but does not handle dynamic computation graphs.…”
Section: Related Workmentioning
confidence: 99%