|
ABSTRACT
A new performance model for dynamic locking is proposed. It is based on a flow diagram and uses only the steady state average values of the variables. It is general enough to handle nonuniform access, shared locks, static locking, multiple transaction classes, and transactions of indeterminate length. The analysis is restricted to the case in which all conflicts are resolved by restarts. It has been shown elsewhere that, under certain conditions, this pure restart policy is as good as, if not better than, a policy that uses both blocking and restarts.
The analysis is straightforward, and the computational complexity of the solution, given some nonrestrictive approximations, does not depend on the input parameters. The solution is also well defined and well behaved. The model's predictions agree well with simulation results.
The model shows that data contention can cause the throughput to thrash, and gives a limit on the workload that will prevent this. It also shows that systems with a particular kind of nonuniform access and systems in which transactions share locks are equivalent to systems in which there is uniform access and only exclusive locking. Static locking has higher throughput, but longer response time, than dynamic locking. Replacing updates by queries in a multiprogramming mix may degrade performance if the queries are longer than the updates.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
 |
1
|
|
| |
2
|
BARD, Y. The modeling of some scheduling strategies for an interactive computer system. In Computer Performance, K. M. Chandy and M. Reiser, Eds. North-Holland, Amsterdam, 1977, pp. 113-137.
|
| |
3
|
BEERI, C., AND OBERMARCK, R. A resource class independent deadlock detection algorithm. In Proceedings of the 7th International Conference on Very Large Data Bases (Cannes, France, Sept. 9-11). ACM, New York, 1981, pp. 166-178.
|
 |
4
|
|
 |
5
|
|
| |
6
|
|
| |
7
|
DENNING, P. J., KAHN, K. C., LEROUDIER, J., POTIER, D., AND SURf, R. Optimal multiprogramming. Acta Inf. 7, 2 (1976), 197-216.
|
| |
8
|
DEVOR, C., AND CARLSON, C. R. Structural locking mechanisms and their effect on database management system performance. Inf. Syst. 7, 4(1982), 345-358.
|
 |
9
|
|
| |
10
|
GALLER, B. I., AND BOS, L. A model of transaction blocking in databases. Perform. Eval. 3 (1983), 95-122.
|
| |
11
|
|
| |
12
|
GRAY, J., HOMAN, P., KORTH, H., AND OBERMARCK, R. A straw man analysis of the probability of waiting and deadlock in a database system. In Proceedings of the 5th Berkeley Workshop on Distributed Data Management and Computer Networks (Feb. 1981), 125.
|
 |
13
|
|
| |
14
|
|
| |
15
|
LIN, W. K., AND NOLTE, J. Performance of two phase locking. In Proceedings of the 6th Berkeley Workshop on Distributed Data Management and Computer Networks (Feb. 1982). 131-160.
|
| |
16
|
LIN, W. K., AND NOLTE, J. Read only transactions and two phase locking. In Proceedings of the 2nd Symposium on Reliability in Distributed Software and Database Systems (Pittsburgh, Pa., 1982).
|
 |
17
|
|
 |
18
|
|
 |
19
|
|
 |
20
|
|
 |
21
|
|
| |
22
|
SHUM, A: W., AND SPIRAKIS, P. G. Performance analysis of concurrency control methods in database systems. In Performance 81, F. J. Kylstra, Ed. North-Holland, Amsterdam, 1981, 1-19.
|
| |
23
|
|
| |
24
|
|
| |
25
|
TAY, Y. C., GOODMAN, N., AND SURI, R. Performance evaluation of locking in databases: A survey. Tech. Rep. TR-17-84, Aiken Computation Lab., Harvard Univ., Cambridge, Mass., Sept. 1984.
|
 |
26
|
|
| |
27
|
THOMASIAN, A. An iterative solution to the queueing network model of a DBMS with dynamic locking. In Proceedings of the 13th Computer Measurement Group Conference (San Diego, Calif., Dec.). 1982, pp. 252-261.
|
 |
28
|
|
REVIEW
"Sharon McCure Kuck : Reviewer"
Performance of locking in database systems is extremely important. We need only
consider the airline reservation system to realize how important the problem is
that these researchers have addressed. Such a database is very large, and it is
both
more...
|