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 language | English (US) |
|---|---|
| Pages (from-to) | 705-714 |
| Number of pages | 10 |
| Journal | IEEE Transactions on Software Engineering |
| Volume | 15 |
| Issue number | 6 |
| DOIs | |
| State | Published - Jan 1 1989 |
Fingerprint
All Science Journal Classification (ASJC) codes
- Software
Cite this
}
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 journal › Article
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
VL - 15
SP - 705
EP - 714
JO - IEEE Transactions on Software Engineering
JF - IEEE Transactions on Software Engineering
SN - 0098-5589
IS - 6
ER -