This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Performance Considerations for an Operating System Transaction Manager
June 1989 (vol. 15 no. 6)
pp. 705-714

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.

[1] R. Agrawal, M. J. Carey, and M. Livny, "Models for studying concurrency control performance: Alternatives and implications,"ACM SIGMOD Int. Conf. Management of Data, 1985, pp. 108-121.
[2] R. Agrawal and D. J. DeWitt, "Integrated concurrency control and recovery mechanisms: Design and performance evaluation,"ACM Trans. Database Syst., vol. 10, pp. 529-564, Dec. 1985.
[3] P.A. Bernstein, V. Hadzilacos, and N. Goodman,Concurrency Control and Recovery in Database Systems, Addison-Wesley, Reading, Mass., 1987.
[4] M. Blasgen, private communication.
[5] M. Brownet al., "The Cedar database management system," inProc. 1981 ACM-SIGMOD Conf. Management of Data, Ann Arbor, MI, June 1981.
[6] M. Carey and M. Stonebraker, "The performance of concurrency control algorithms for database management systems," inProc. VLDB, 1984, pp. 107-118.
[7] A. Chang, private communication.
[8] C. J. Date,A Guide to DB2. Reading, MA: Addison-Wesley, 1986.
[9] P. Franaszek and J. Robinson, "Limitations of concurrency in transaction processing," IBM Thomas J. Watson Research Center, Rep. RC10151, Aug. 1983.
[10] B. I. Galler, "Concurrency control performance issues," Ph.D. thesis, Comput. Sci. Dept., Univ. Toronto, Sept. 1982.
[11] J. Gray, "Notes on database operation systems," inOperating Systems: An Advanced Course(Lecture Notes in Computer Science, vol. 60) Berlin: Springer-Verlag, 1978.
[12] J. N. Grayet al., "The recovery manager of the System R database manager, "ACM Comput. Surveys, vol. 13, pp. 223-242, June 1981.
[13] T. Haerder and A. Reuter, "Principles of transaction-oriented data-base recovery,"ACM Comput. Surveys, vol. 15, pp. 287-317, Dec. 1983.
[14] A. Kumar and M. Stonebraker, "Performance evaluation of an operating system transaction manager,"VLDB, 1987.
[15] H. T. Kung and J. T. Robinson, "On optimistic methods for concurrency control,"ACM Trans. Database Syst., vol. 6, pp. 213-226, June 1981.
[16] W. Lin and J. Nolte, "Basic timestamp, multiple version timestamp, and two-phase locking," inProc. 9th VLDB Conf., Nov. 1983.
[17] J. G. Mitchell and J. Dion, "A comparison of two network-based file servers,"Commun. ACM, vol. 25, pp. 233-245, Apr. 1982.
[18] E. Muelleret al., "A nested transaction mechanism for LOCUS," inProc. 9th Symp. Operating Systems Principles, Oct. 1983.
[19] C. Pu and J. Noe, "Design of nested transactions in Eden," Dep. Comput. Sci., Univ. Washington, Seattle, Tech. Rep. 85-12-03, Feb. 1986.
[20] D. Reed, "Naming and synchronization in a decentralized computer system," Ph.D. dissertation, Dep. Elec. Eng. Comput. Sci., M.I.T., 1978.
[21] A. Reuter, "Performance analysis of recovery techniques,"ACM Trans. Database Syst., vol. 9, no. 4, pp. 526-559, Dec. 1984.
[22] A. Spector and P. Schwartz, "Transactions: A construct for reliable distributed computing,"Operating Syst. Rev., vol. 17, no. 2, Apr. 1983.
[23] M. Stonebraker, "Operating System Support for Database Management,"Comm. ACM, Vol. 24, No. 7, July 1981, pp. 412- 418.
[24] M. Stonebraker, "Virtual memory transaction management,"ACM Oper. Syst. Rev., vol. 18, no. 2, Apr. 1984.
[25] M. Stonebrakeret al., "Problems in supporting data base transactions in an operating system transaction manager,"Operaring Syst. Rev., vol. 19, no. 1, Jan. 1985.
[26] I. Traiger, "Virtual memory management for database systems,"ACM Oper. Syst. Rev., vol. 16, no. 4, pp. 26-48, Oct. 1983.
[27] Y. Tay and R. Suri, "Choice and performance in locking for databases," inProc. 10th VLDB Conf., Sept. 1984.
[28] R. Thomas, "A majority consensus approach to concurrency control,"ACM Trans. Database Syst., vol. 4, pp. 180-209, June 1979.

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
Usage of this product signifies your acceptance of the Terms of Use.