Show simple item record

dc.contributor.advisorSnodgrass, Richard T.en
dc.contributor.authorSuh, Youngkyoon
dc.creatorSuh, Youngkyoonen
dc.date.accessioned2015-06-03T20:42:55Zen
dc.date.available2015-06-03T20:42:55Zen
dc.date.issued2015en
dc.identifier.urihttp://hdl.handle.net/10150/556213en
dc.description.abstractModern DBMSes are designed to support many transactions running simultaneously. DBMS thrashing is indicated by the existence of a sharp drop in transaction throughput. The thrashing behavior in DBMSes is a serious concern to DBAs engaged in on-line transaction processing (OLTP) and on-line analytical processing (OLAP) systems, as well as to DBMS implementors developing technologies related to concurrency control. If thrashing is prevalent in a DBMS, thousands of transactions may be aborted, resulting in little progress in transaction throughput over time. From an engineering perspective, therefore, it is of critical importance to understand the factors of DBMS thrashing. However, understanding the origin of modern DBMSes' thrashing is challenging, due to many factors that may interact. The existing literature on thrashing exhibits the following weaknesses: (i) methodologies have been based on simulation and analytical studies, rather than on empirical analysis on real DBMSes, (ii) scant attention has been paid to the associations between factors, and (iii) studies have been restricted to one specific DBMS rather than across multiple DBMSes. This dissertation aims at better understanding the thrashing phenomenon across multiple DBMSes. We identify the underlying causes and 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 engineering implications for fundamental improvements in transaction processing. Our model also guides database researchers to refine this causal model, by looking into other unknown factors.
dc.language.isoen_USen
dc.publisherThe University of Arizona.en
dc.rightsCopyright © is held by the author. Digital access to this material is made possible by the University Libraries, University of Arizona. Further transmission, reproduction or presentation (such as public display or performance) of protected items is prohibited except with permission of the author.en
dc.subjectDBMS Thrashingen
dc.subjectEngineering Implicationsen
dc.subjectErgalicsen
dc.subjectStatistical Analysisen
dc.subjectTransactionsen
dc.subjectComputer Scienceen
dc.subjectA Structural Causal Modelen
dc.titleExploring Causal Factors of DBMS Thrashingen_US
dc.typetexten
dc.typeElectronic Dissertationen
dc.contributor.chairSnodgrass, Richard T.en
thesis.degree.grantorUniversity of Arizonaen
thesis.degree.leveldoctoralen
dc.contributor.committeememberSnodgrass, Richard T.en
dc.contributor.committeememberCurrim, Sabahen
dc.contributor.committeememberDowney, Peter J.en
dc.contributor.committeememberKececioglu, John K.en
thesis.degree.disciplineGraduate Collegeen
thesis.degree.disciplineComputer Scienceen
thesis.degree.namePh.D.en
refterms.dateFOA2018-06-24T07:20:30Z
html.description.abstractModern DBMSes are designed to support many transactions running simultaneously. DBMS thrashing is indicated by the existence of a sharp drop in transaction throughput. The thrashing behavior in DBMSes is a serious concern to DBAs engaged in on-line transaction processing (OLTP) and on-line analytical processing (OLAP) systems, as well as to DBMS implementors developing technologies related to concurrency control. If thrashing is prevalent in a DBMS, thousands of transactions may be aborted, resulting in little progress in transaction throughput over time. From an engineering perspective, therefore, it is of critical importance to understand the factors of DBMS thrashing. However, understanding the origin of modern DBMSes' thrashing is challenging, due to many factors that may interact. The existing literature on thrashing exhibits the following weaknesses: (i) methodologies have been based on simulation and analytical studies, rather than on empirical analysis on real DBMSes, (ii) scant attention has been paid to the associations between factors, and (iii) studies have been restricted to one specific DBMS rather than across multiple DBMSes. This dissertation aims at better understanding the thrashing phenomenon across multiple DBMSes. We identify the underlying causes and 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 engineering implications for fundamental improvements in transaction processing. Our model also guides database researchers to refine this causal model, by looking into other unknown factors.


Files in this item

Thumbnail
Name:
azu_etd_13776_sip1_m.pdf
Size:
2.772Mb
Format:
PDF

This item appears in the following Collection(s)

Show simple item record