Answer:
A less expensive alternative is simply to invoke the algorithm at defined intervals—for example,
Once per hour or whenever CPU utilization drops below 40 percent. (A deadlock eventually cripples system throughput and causes CPU utilization to drop.) If the detection algorithm is invoked at arbitrary points in time, the resource Graph may contain many cycles. In this case, we generally cannot tell which of the many deadlocked processes “caused” the deadlock.
A less expensive alternative is simply to invoke the algorithm at defined intervals—for example,
Once per hour or whenever CPU utilization drops below 40 percent. (A deadlock eventually cripples system throughput and causes CPU utilization to drop.) If the detection algorithm is invoked at arbitrary points in time, the resource Graph may contain many cycles. In this case, we generally cannot tell which of the many deadlocked processes “caused” the deadlock.
You may be interested in:
OS Deadlocks MCQs