2017
DOI: 10.1109/tnet.2017.2731986
|View full text |Cite
|
Sign up to set email alerts
|

Expeditus: Congestion-Aware Load Balancing in Clos Data Center Networks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
15
0

Year Published

2017
2017
2022
2022

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 21 publications
(15 citation statements)
references
References 33 publications
0
15
0
Order By: Relevance
“…Expeditus [30] distributed congestionaware load balancing protocol three-level Clos topology web search and data mining workloads For mice flows, Expeditus outperforms ECMP by up to 45% in tail flow completion times and by up to 38% in mean flow completion time for elephant flows in 3-tier Clos networks.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…Expeditus [30] distributed congestionaware load balancing protocol three-level Clos topology web search and data mining workloads For mice flows, Expeditus outperforms ECMP by up to 45% in tail flow completion times and by up to 38% in mean flow completion time for elephant flows in 3-tier Clos networks.…”
Section: Discussionmentioning
confidence: 99%
“…Niagara [27] is another traffic-splitting solution for commodity switches which offers similar performance to MicroTe [28]. A promising distributed congestion-aware load balancing solution is proposed in [29], [30] and referred to as Expeditus. Expeditus is targeted at general 3-tier Clos topologies and conveys load balancing to network edge using local congestion monitoring.…”
Section: Scope and Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Many researchers had proposed congestion-aware switching techniques to balance the data center loads. However, from the assessment, it is evident that most of the schemes suffer from the congestion mismatch in an asymmetric condition [12,18].…”
Section: Related Workmentioning
confidence: 99%
“…For example, flows from many hosts may pass through a ToR switch giving it further knowledge to perform scheduling and allocation optimizations. Some examples of this approach include RCP [86], PDQ [87], CONGA [106], Expeditus [107], and RackCC [108]. RCP and PDQ perform in-network rate allocation and assignment by allowing switches and end-hosts to communicate using custom headers, CONGA gets help from switches to perform flowlet based load balancing in leaf-spine topologies, Expeditus performs flow based load balancing by implementing custom Layer 2 headers and localized monitoring of congestion at the switches, and RackCC uses ToR switches as means to share congestion information among many flows between the same source and destination racks to help them converge faster to proper transmission rates.…”
Section: Scheme Benefits Drawbacksmentioning
confidence: 99%