2017
DOI: 10.48550/arxiv.1702.07802
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Near-Data Scheduling for Data Centers with Multiple Levels of Data Locality

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2017
2017
2019
2019

Publication Types

Select...
3
1

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(8 citation statements)
references
References 0 publications
0
8
0
Order By: Relevance
“…is signi cant improvement over JSQ-MaxWeight algorithm shows that JSQ-MaxWeight is not delay optimal and supports the possibility that the GB-PANDAS algorithm is delay optimal in a larger region than the JSQ-MaxWeight algorithm. By the intuition we got from the delay optimality proof of the JSQ-MaxWeight algorithm for two locality levels in [32], [37], [30], and [34], we simulated the system under a load for which we believe JSQ-MaxWeight is delay optimal. Figure 5 shows the result for this speci c load and we see that both the GB-PANDAS and JSQ-MaxWeight algorithms have the same performance at high loads, which again supports our guess on delay optimality of our proposed algorithm.…”
Section: Simulation Resultsmentioning
confidence: 99%
“…is signi cant improvement over JSQ-MaxWeight algorithm shows that JSQ-MaxWeight is not delay optimal and supports the possibility that the GB-PANDAS algorithm is delay optimal in a larger region than the JSQ-MaxWeight algorithm. By the intuition we got from the delay optimality proof of the JSQ-MaxWeight algorithm for two locality levels in [32], [37], [30], and [34], we simulated the system under a load for which we believe JSQ-MaxWeight is delay optimal. Figure 5 shows the result for this speci c load and we see that both the GB-PANDAS and JSQ-MaxWeight algorithms have the same performance at high loads, which again supports our guess on delay optimality of our proposed algorithm.…”
Section: Simulation Resultsmentioning
confidence: 99%
“…One could consider developing a P2MP joint scheduling and routing scheme with throughput-optimality as the objective. However, in general, throughput-optimality does not necessarily lead to highest performance (e.g., lowest latency) [54], [55].…”
Section: Related Workmentioning
confidence: 99%
“…In fact, λL ,m is the decomposition of λL. Assuming that a server can afford at most load 1 for all local, rack-local, and remote tasks, the capacity region can be characterized as follows [12], [13]:…”
Section: A Capacity Region Realizationmentioning
confidence: 99%