Previous | Next --- Slide 50 of 69
Back to Lecture Thumbnails
1_1

NO_WAIT and WAIT_DIE approaches perform the best because it is low cost to figure out whether there is a conflict and kill the transactions immediately.

However, DL_DETECT plummets because this protocol usually keeps a separate thread running in the background trying to detect deadlocks. You don't want to have it running all the time since you're burning cycles for no reason. Instead, you want to set a delay where every so often this thread checks for deadlocks and kills transactions, but then this delay to kill the transactions worsens performance.