2011
DOI: 10.1007/978-3-642-19260-9_3
|View full text |Cite
|
Sign up to set email alerts
|

Evolution of Cache Replacement Policies to Track Heavy-Hitter Flows

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2011
2011
2024
2024

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(2 citation statements)
references
References 11 publications
0
2
0
Order By: Relevance
“…Initial naive proposals to keep counters for each flow [34], [13] are not scalable when there exist millions of flows, which is common in today's network environment. There have been extensive researches on reducing the overheads of keeping per flow counters [27], [18], [12], [41], [40] to find the accurate estimate of the rates of aggressive flows. In contrast, LAPS merely needs to identify the top aggressive flows without accurately estimating the rates of all flows.…”
Section: Benefit Of Limiting Migration To Only Top Flowsmentioning
confidence: 99%
“…Initial naive proposals to keep counters for each flow [34], [13] are not scalable when there exist millions of flows, which is common in today's network environment. There have been extensive researches on reducing the overheads of keeping per flow counters [27], [18], [12], [41], [40] to find the accurate estimate of the rates of aggressive flows. In contrast, LAPS merely needs to identify the top aggressive flows without accurately estimating the rates of all flows.…”
Section: Benefit Of Limiting Migration To Only Top Flowsmentioning
confidence: 99%
“…The algorithm detects elephant flows with small memory space, whereas it cannot estimate the size of detected flows. Memory‐aware heavy‐hitter detection schemes may also be found .…”
Section: Related Workmentioning
confidence: 99%