2016
DOI: 10.14778/2977797.2977799
|View full text |Cite
|
Sign up to set email alerts
|

Tempo

Abstract: Multi-tenant database systems have a component called the Resource Manager, or RM that is responsible for allocating resources to tenants. RMs today do not provide direct support for performance objectives such as: "Average job response time of tenant A must be less than two minutes", or "No more than 5% of tenant B's jobs can miss the deadline of 1 hour." Thus, DBAs have to tinker with the RM's lowlevel configuration settings to meet such objectives. We propose a framework called Tempo that brings simplicity,… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 20 publications
(3 citation statements)
references
References 38 publications
0
3
0
Order By: Relevance
“…This system aims to map specific interfaces of the individual systems regardless of their individual differences; thus, interoperability. In a similar work conducted by Tan et al [62], an interface known as Tempo was created for DBAs to have a simpler way of specifying performance objectives and optimize Resource Manager Configurations. This is to optimize job processing time allocations and make sure deadlines are not missed.…”
Section: Overview Of the Nosql Databasesmentioning
confidence: 99%
“…This system aims to map specific interfaces of the individual systems regardless of their individual differences; thus, interoperability. In a similar work conducted by Tan et al [62], an interface known as Tempo was created for DBAs to have a simpler way of specifying performance objectives and optimize Resource Manager Configurations. This is to optimize job processing time allocations and make sure deadlines are not missed.…”
Section: Overview Of the Nosql Databasesmentioning
confidence: 99%
“…Most of the strategies described here focus on reducing the consumption of the required resources during data replication without taking into account the economic cost of replication (Bai et al, 2013;Dabas and Aggarwal, 2019;Edwin et al, 2019;Kumar et al, 2014;Lee et al, 2015;Long et al, 2014;Liu et al, 2013;Mansouri and Javidi, 2018;Pu et al, 2015;Sakr et al, 2011;Tan and Babu, 2016;Wei et al, 2010) . Most of them were interested in finding the optimal number of replicas (He et al, 2018) or replica placement (Zhang et al, 2015) because of their effects on performance.…”
Section: Replication Strategies Without Taking Into Account the Econo...mentioning
confidence: 99%
“…Most of the strategies described here focus on reducing the consumption of the required resources during data replication without taking into account the economic cost of replication (Bai et al, 2013;Dabas and Aggarwal, 2019;Edwin et al, 2019;Kumar et al, 2014;Lee et al, 2015;Long et al, 2014;Liu et al, 2013;Mansouri and Javidi, 2018;Pu et al, 2015;Sakr et al, 2011;Tan and Babu, 2016;Wei et al, 2010) . Most of them were interested in finding the optimal number of replicas (He et al, 2018) or replica placement (Zhang et al, 2015) because of their effects on performance.…”
Section: Replication Strategies Without Taking Into Account the Econo...mentioning
confidence: 99%