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

Adaptive Stream Processing using Dynamic Batch Sizing

Abstract: AcknowledgementsMany thanks to Yuan Zhong, Ion Stoica and Scott Shenker for making this thesis possible. Also thanks to David Zats, Shivaram Venkataraman, and Neeraja Yadwadkar for providing feedback on earlier versions of the text.Finally, a very special thanks to both my advisers, Scott Shenker and Ion Stoica, for guiding me through my ups and downs in life and putting up with my idiosyncrasies. 2 AbstractThe need for real-time processing of "big data" has led to the development of frameworks for distributed… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
76
0
1

Year Published

2016
2016
2024
2024

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 102 publications
(78 citation statements)
references
References 19 publications
1
76
0
1
Order By: Relevance
“…Lohrmann et al [37] adaptively adjusted the buffer sizes and performs task chaining according to the QoS constraints. Das et al [23] used dynamic batch sizing for stream processing in Apache Spark to avoid queuing delays as the input data rate changes. Venkataraman et al [50] dynamically adjusted the number of batches that were grouped together for scheduling.…”
Section: Related Workmentioning
confidence: 99%
“…Lohrmann et al [37] adaptively adjusted the buffer sizes and performs task chaining according to the QoS constraints. Das et al [23] used dynamic batch sizing for stream processing in Apache Spark to avoid queuing delays as the input data rate changes. Venkataraman et al [50] dynamically adjusted the number of batches that were grouped together for scheduling.…”
Section: Related Workmentioning
confidence: 99%
“…Storm [66] uses Zookeeper [6] to coordinate backpressure across nodes. Das et al [19] propose dynamically adjusting batch sizes to improve latency and throughput. Contrary to these approaches, Wisp's rate limiting approach does not assume knowledge of the full service topology, dynamically computes rate limits based on measured resource utilization instead of static thresholds, is multi-tenant aware, and does not require centralized coordination.…”
Section: Related Workmentioning
confidence: 99%
“…foreach Oi do 6 Let p ik be the node in Si that has the largest OF increase δ ik ; 7 P ← P ∪ {p ik }; Si ← Si − {p ik }; 8 usage = N ; 9 if P = ∅ & N > R then return P; 10 while usage < R do 11 Candidates ← ∅; 12 foreach Oi do 13 Let p ik be the node in Si that has the largest OF increase δ ik ;…”
Section: Algorithm 4: Planfulltopology(p R T )mentioning
confidence: 99%
“…Input: The amount of available resources R; Topology T ; Output: Partial replication plan P; 1 Initialize: decompose the complete topology T into sub-topologies: T S1, T S2, ... ; 2 P ← ∅, SA ← ∅, usage ← 0; 3 if R < Number of operators in T then 4 Return P ; 5 foreach Sub-Topology T Si do 6 Ni ← Number of operators in T Si;…”
Section: Algorithm 5: Structureaware(rt )mentioning
confidence: 99%