Performance Considerations for an Operating System Transaction Manager

Akhil Kumar, Michael Stonebraker

Research output: Contribution to journalArticle

2 Citations (Scopus)

Abstract

Results of a previous comparison study [14] between a conventional transaction manager and an operating system (OS) transaction manager have indicated that the OS transaction manager incurs a severe performance penalty and appears to be feasible only in special circumstances. The present study considers three approaches for enhancing the performance of an OS transaction manager. The first strategy is to improve performance by reducing the cost of lock acquisition and by compressing the log. The second strategy explores the possibility of still further improvements from additional semantics to be built into an OS transaction system. The last strategy is to use a modified index structure that makes update operations less expensive to perform. The results of this study show that the OS will have to implement essentially all of the specialized tactics for transaction management that are currently used by a database management system (DBMS) in order to match DBMS performance.

Original languageEnglish (US)
Pages (from-to)705-714
Number of pages10
JournalIEEE Transactions on Software Engineering
Volume15
Issue number6
DOIs
StatePublished - Jan 1 1989

Fingerprint

Managers
Semantics
Costs

All Science Journal Classification (ASJC) codes

  • Software

Cite this

@article{6b36b6abcaea4c8991ffa548d3d0abec,
title = "Performance Considerations for an Operating System Transaction Manager",
abstract = "Results of a previous comparison study [14] between a conventional transaction manager and an operating system (OS) transaction manager have indicated that the OS transaction manager incurs a severe performance penalty and appears to be feasible only in special circumstances. The present study considers three approaches for enhancing the performance of an OS transaction manager. The first strategy is to improve performance by reducing the cost of lock acquisition and by compressing the log. The second strategy explores the possibility of still further improvements from additional semantics to be built into an OS transaction system. The last strategy is to use a modified index structure that makes update operations less expensive to perform. The results of this study show that the OS will have to implement essentially all of the specialized tactics for transaction management that are currently used by a database management system (DBMS) in order to match DBMS performance.",
author = "Akhil Kumar and Michael Stonebraker",
year = "1989",
month = "1",
day = "1",
doi = "10.1109/32.24724",
language = "English (US)",
volume = "15",
pages = "705--714",
journal = "IEEE Transactions on Software Engineering",
issn = "0098-5589",
publisher = "Institute of Electrical and Electronics Engineers Inc.",
number = "6",

}

Performance Considerations for an Operating System Transaction Manager. / Kumar, Akhil; Stonebraker, Michael.

In: IEEE Transactions on Software Engineering, Vol. 15, No. 6, 01.01.1989, p. 705-714.

Research output: Contribution to journalArticle

TY - JOUR

T1 - Performance Considerations for an Operating System Transaction Manager

AU - Kumar, Akhil

AU - Stonebraker, Michael

PY - 1989/1/1

Y1 - 1989/1/1

N2 - Results of a previous comparison study [14] between a conventional transaction manager and an operating system (OS) transaction manager have indicated that the OS transaction manager incurs a severe performance penalty and appears to be feasible only in special circumstances. The present study considers three approaches for enhancing the performance of an OS transaction manager. The first strategy is to improve performance by reducing the cost of lock acquisition and by compressing the log. The second strategy explores the possibility of still further improvements from additional semantics to be built into an OS transaction system. The last strategy is to use a modified index structure that makes update operations less expensive to perform. The results of this study show that the OS will have to implement essentially all of the specialized tactics for transaction management that are currently used by a database management system (DBMS) in order to match DBMS performance.

AB - Results of a previous comparison study [14] between a conventional transaction manager and an operating system (OS) transaction manager have indicated that the OS transaction manager incurs a severe performance penalty and appears to be feasible only in special circumstances. The present study considers three approaches for enhancing the performance of an OS transaction manager. The first strategy is to improve performance by reducing the cost of lock acquisition and by compressing the log. The second strategy explores the possibility of still further improvements from additional semantics to be built into an OS transaction system. The last strategy is to use a modified index structure that makes update operations less expensive to perform. The results of this study show that the OS will have to implement essentially all of the specialized tactics for transaction management that are currently used by a database management system (DBMS) in order to match DBMS performance.

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

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

U2 - 10.1109/32.24724

DO - 10.1109/32.24724

M3 - Article

AN - SCOPUS:0024680766

VL - 15

SP - 705

EP - 714

JO - IEEE Transactions on Software Engineering

JF - IEEE Transactions on Software Engineering

SN - 0098-5589

IS - 6

ER -