DOI: 10.1007/978-3-540-85654-2_71
|View full text |Cite
|
Sign up to set email alerts
|

Compressing Very Large Database Workloads for Continuous Online Index Selection

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Publication Types

Select...
3
3

Relationship

1
5

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 10 publications
0
5
0
Order By: Relevance
“…However, the distance function strictly focuses on index selection, the entire workload must be known in advance, and sampling is performed instead of classification. Though stream-oriented, the approach in [6] does not guarantee consistency of classification results or a class. Data streams clustering approaches like [7] often employ on-line versions of the k-Means algorithm.…”
Section: Problem Descriptionmentioning
confidence: 97%
“…However, the distance function strictly focuses on index selection, the entire workload must be known in advance, and sampling is performed instead of classification. Though stream-oriented, the approach in [6] does not guarantee consistency of classification results or a class. Data streams clustering approaches like [7] often employ on-line versions of the k-Means algorithm.…”
Section: Problem Descriptionmentioning
confidence: 97%
“…Offline tasks are those that do not require or do not allow processing each query separately, and can be implemented as typical batch jobs. For example, query clustering is important for workload summarization [16], but does not require real-time labeling of individual queries.…”
Section: System Architecturementioning
confidence: 99%
“…Workload summarization for index recommendation: The goal [3,16] is to find a representative sample of the workload as input to further database administration, tuning, and testing tasks [3,33]. In particular, workload summarization aids index recommendation, since the recommendation process is typically quadratic in the size of the workload [3].…”
Section: Applicationsmentioning
confidence: 99%
“…Because it took too long to estimate the cost of such a large workload Fig. 3 Final workload cost as a function of number of iterations for MG database for cold start and then to automatically select indexes, both workloads were compressed by a method presented in [16]. The final numbers of queries after compression were 289 for MG, and 62 for WA.…”
Section: Complex Workloadsmentioning
confidence: 99%