2015
DOI: 10.1007/978-3-319-15350-6_7
|View full text |Cite
|
Sign up to set email alerts
|

Scaling Up Mixed Workloads: A Battle of Data Freshness, Flexibility, and Scheduling

Abstract: Abstract. The common "one size does not fit all" paradigm isolates transactional and analytical workloads into separate, specialized database systems. Operational data is periodically replicated to a data warehouse for analytics. Competitiveness of enterprises today, however, depends on real-time reporting on operational data, necessitating an integration of transactional and analytical processing in a single database system. The mixed workload should be able to query and modify common data in a shared schema.… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

2
17
0

Year Published

2015
2015
2024
2024

Publication Types

Select...
5
2
1

Relationship

2
6

Authors

Journals

citations
Cited by 15 publications
(19 citation statements)
references
References 12 publications
(17 reference statements)
2
17
0
Order By: Relevance
“…Task-based execution is used in numerous modern DBMS and research prototypes, including SAP HANA [18], IBM DB2 BLU [20], HyPer [16], etc. Task scheduling works for both OLTP and OLAP workloads, although we have shown that workload management, e.g., through task prioritization, is essential to avoid the OLAP workload dominating over a concurrent OLTP workload [19]. The main reason is that analytical workloads are typically more aggressively parallelized than transactional workloads.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Task-based execution is used in numerous modern DBMS and research prototypes, including SAP HANA [18], IBM DB2 BLU [20], HyPer [16], etc. Task scheduling works for both OLTP and OLAP workloads, although we have shown that workload management, e.g., through task prioritization, is essential to avoid the OLAP workload dominating over a concurrent OLTP workload [19]. The main reason is that analytical workloads are typically more aggressively parallelized than transactional workloads.…”
Section: Related Workmentioning
confidence: 99%
“…We run this algorithm with the three input sizes shown in Table 2. Initially, keys and values in the input data structures are filled with random integers between [0, 99], and [0,19] respectively. The grouping is hash-based, using a C++11 std::unordered_map.…”
Section: Data Set Matrix Sizementioning
confidence: 99%
“…Operations are encapsulated in tasks, and a pool of worker threads is used to process them. In our previous work, we showed how task scheduling can be used in a NUMA-agnostic main-memory column-store to efficiently process mixed OLTP and OLAP workloads [28,29]. We showed how stealing and a flexible concurrency level can help to saturate CPU resources without oversubscribing them, and how a concurrency hint can be used to adjust the task granularity of analytical partitionable operations to avoid unnecessary scheduling overhead.…”
Section: Related Workmentioning
confidence: 99%
“…Modern database systems need to support mixed workloads of online transaction processing (OLTP) and online analytical processing (OLAP) workloads [11,17,18]. OLTP workloads contain short-lived, light transactions which read or update small portions of data, while OLAP workloads contain long-running, heavy transactions which reads large portions of data.…”
Section: Introductionmentioning
confidence: 99%
“…However, this approach requires an extremely expensive hardware. Previous work such as Hyper [11,18] focuses on scaling up mixed workloads in a single hardware host, which eventually limits the maximum scalability of analytical query processing.…”
Section: Introductionmentioning
confidence: 99%