“…In 2PL with GW policy, a transaction is blocked if it requests a data granule locked by another transaction, and the restart is initiated only when there is a deadlock. Blocking transactions, however, has great negative effect on system performance (Franaszek et al, 1985) (Tayet al, 1985a (Thomasian, 1991). Especially, as the level of data contention increases (e.g., by increasing the multiprogramming level (M), i.e., the total number of transactions running concurrently in a TP system), the interaction between data contention and 2PL with GW policy causes such a snowball effect that the blocked transactions hold locks that they have acquired and result in further blocking (Franaszek et al, 1985) (Tay et al, 1985b) (Thomasian, 1991).…”