The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.06 - June (1989 vol.15)
pp: 705-714
ABSTRACT
<p>Results of a previous comparison study (A. Kumar and M. Stonebraker, 1987) between a conventional transaction manager and an operating system (OS) transaction manager indicated that the OS transaction manager incurs a severe performance penalty and appears to be feasible only in special circumstances. Three approaches for enhancing the performance of an OS transaction manager are considered. 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 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.</p>
INDEX TERMS
log compressing; performance; considerations; operating system transaction manager; conventional transaction manager; OS transaction manager; performance penalty; lock acquisition; additional semantics; OS transaction system; modified index structure; update operations; transaction management; database management system; DBMS performance; data structures; database management systems; operating systems (computers); performance evaluation; software reliability; transaction processing
CITATION
A. Kumar, M. Stonebraker, "Performance Considerations for an Operating System Transaction Manager", IEEE Transactions on Software Engineering, vol.15, no. 6, pp. 705-714, June 1989, doi:10.1109/32.24724
32 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool