An empirical study of transaction throughput thrashing across multiple relational DBMSes

Young Kyoon Suh, Richard Thomas Snodgrass, Sabah Currim

Research output: Contribution to journalArticle

3 Citations (Scopus)

Abstract

Modern DBMSes are designed to support many transactions running simultaneously. DBMS thrashing is indicated by the existence of a sharp drop in transaction throughput. Thrashing behavior in DBMSes is a serious concern to database administrators (DBAs) as well as to DBMS implementers. From an engineering perspective, therefore, it is of critical importance to understand the causal factors of DBMS thrashing. However, understanding the origin of thrashing in modern DBMSes is challenging, due to many factors that may interact with each other.This article aims to better understand the thrashing phenomenon across multiple DBMSes. We identify some of the underlying causes of DBMS thrashing. We then propose a novel structural causal model to explicate the relationships between various factors contributing to DBMS thrashing. Our model derives a number of specific hypotheses to be subsequently tested across DBMSes, providing empirical support for this model as well as important engineering implications for improvements in transaction processing.

Original languageEnglish (US)
JournalInformation Systems
DOIs
StateAccepted/In press - Nov 17 2015

Fingerprint

Throughput
Processing

Keywords

  • DBMS Thrashing
  • Empirical Study
  • Factors
  • Structural Causal Model
  • Throughput
  • Transaction

ASJC Scopus subject areas

  • Software
  • Information Systems
  • Hardware and Architecture

Cite this

An empirical study of transaction throughput thrashing across multiple relational DBMSes. / Suh, Young Kyoon; Snodgrass, Richard Thomas; Currim, Sabah.

In: Information Systems, 17.11.2015.

Research output: Contribution to journalArticle

@article{b25958046f974cda88399364fdeac878,
title = "An empirical study of transaction throughput thrashing across multiple relational DBMSes",
abstract = "Modern DBMSes are designed to support many transactions running simultaneously. DBMS thrashing is indicated by the existence of a sharp drop in transaction throughput. Thrashing behavior in DBMSes is a serious concern to database administrators (DBAs) as well as to DBMS implementers. From an engineering perspective, therefore, it is of critical importance to understand the causal factors of DBMS thrashing. However, understanding the origin of thrashing in modern DBMSes is challenging, due to many factors that may interact with each other.This article aims to better understand the thrashing phenomenon across multiple DBMSes. We identify some of the underlying causes of DBMS thrashing. We then propose a novel structural causal model to explicate the relationships between various factors contributing to DBMS thrashing. Our model derives a number of specific hypotheses to be subsequently tested across DBMSes, providing empirical support for this model as well as important engineering implications for improvements in transaction processing.",
keywords = "DBMS Thrashing, Empirical Study, Factors, Structural Causal Model, Throughput, Transaction",
author = "Suh, {Young Kyoon} and Snodgrass, {Richard Thomas} and Sabah Currim",
year = "2015",
month = "11",
day = "17",
doi = "10.1016/j.is.2016.12.004",
language = "English (US)",
journal = "Information Systems",
issn = "0306-4379",
publisher = "Elsevier Limited",

}

TY - JOUR

T1 - An empirical study of transaction throughput thrashing across multiple relational DBMSes

AU - Suh, Young Kyoon

AU - Snodgrass, Richard Thomas

AU - Currim, Sabah

PY - 2015/11/17

Y1 - 2015/11/17

N2 - Modern DBMSes are designed to support many transactions running simultaneously. DBMS thrashing is indicated by the existence of a sharp drop in transaction throughput. Thrashing behavior in DBMSes is a serious concern to database administrators (DBAs) as well as to DBMS implementers. From an engineering perspective, therefore, it is of critical importance to understand the causal factors of DBMS thrashing. However, understanding the origin of thrashing in modern DBMSes is challenging, due to many factors that may interact with each other.This article aims to better understand the thrashing phenomenon across multiple DBMSes. We identify some of the underlying causes of DBMS thrashing. We then propose a novel structural causal model to explicate the relationships between various factors contributing to DBMS thrashing. Our model derives a number of specific hypotheses to be subsequently tested across DBMSes, providing empirical support for this model as well as important engineering implications for improvements in transaction processing.

AB - Modern DBMSes are designed to support many transactions running simultaneously. DBMS thrashing is indicated by the existence of a sharp drop in transaction throughput. Thrashing behavior in DBMSes is a serious concern to database administrators (DBAs) as well as to DBMS implementers. From an engineering perspective, therefore, it is of critical importance to understand the causal factors of DBMS thrashing. However, understanding the origin of thrashing in modern DBMSes is challenging, due to many factors that may interact with each other.This article aims to better understand the thrashing phenomenon across multiple DBMSes. We identify some of the underlying causes of DBMS thrashing. We then propose a novel structural causal model to explicate the relationships between various factors contributing to DBMS thrashing. Our model derives a number of specific hypotheses to be subsequently tested across DBMSes, providing empirical support for this model as well as important engineering implications for improvements in transaction processing.

KW - DBMS Thrashing

KW - Empirical Study

KW - Factors

KW - Structural Causal Model

KW - Throughput

KW - Transaction

UR - http://www.scopus.com/inward/record.url?scp=85016460407&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=85016460407&partnerID=8YFLogxK

U2 - 10.1016/j.is.2016.12.004

DO - 10.1016/j.is.2016.12.004

M3 - Article

AN - SCOPUS:85016460407

JO - Information Systems

JF - Information Systems

SN - 0306-4379

ER -