Proceedings. 20th International Conference on Data Engineering
DOI: 10.1109/icde.2004.1320010
|View full text |Cite
|
Sign up to set email alerts
|

Load shedding for aggregation queries over data streams

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
238
0
1

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 203 publications
(239 citation statements)
references
References 21 publications
0
238
0
1
Order By: Relevance
“…Several research groups have picked up the challenge of replacing the previously dominant strategy of data quality degradation, i.e., load shedding (Babcock, Datar & Motwani, 2004;Tatbul, Ç etintemel & Zdonik, 2007), with resource elasticity. Nevertheless, most of the first publications focus on an optimal resource configuration only when deploying a topology and do not consider any updates at runtime, e.g., Setty et al (2014) for pub/sub systems or Florescu & Kossmann (2009) for database systems.…”
Section: Related Workmentioning
confidence: 99%
“…Several research groups have picked up the challenge of replacing the previously dominant strategy of data quality degradation, i.e., load shedding (Babcock, Datar & Motwani, 2004;Tatbul, Ç etintemel & Zdonik, 2007), with resource elasticity. Nevertheless, most of the first publications focus on an optimal resource configuration only when deploying a topology and do not consider any updates at runtime, e.g., Setty et al (2014) for pub/sub systems or Florescu & Kossmann (2009) for database systems.…”
Section: Related Workmentioning
confidence: 99%
“…Node s forwards a sequence of tuples to its parent P s during a round. It numbers these sequentially, e.g., (1,2,3,4,5,6). The highest sequence number is labeled n max = 6.…”
Section: Lazaridis Et Almentioning
confidence: 99%
“…Our work complements data stream systems using load shedding [22,1]. A data stream processor often needs to ''drop'' tuples at the input of operators, if its capacity does not suffice.…”
mentioning
confidence: 99%
“…In this case, we need to decide whether s is to be discarded or admitted into S 1 [W 1 ], and if it is to be admitted, which of the existing tuples is to be discarded. An algorithm that makes this decision is called a load-shedding strategy [4,7,17]. Due to load-shedding, only a fraction of the true result will actually be produced.…”
Section: Max-subsetmentioning
confidence: 99%
“…The stream system could instead (or also) be CPU-limited, i.e., the rate of incoming tuples is higher than can be processed. Load-shedding for the CPU-limited case has been considered in [4,17]. Sampling from a window is addressed in [3], but only for a single stream and not for a join result.…”
Section: Related Workmentioning
confidence: 99%