Difference between Monitor.Pulse and Monitor.PulseAll

Question

Monitor.PulseAll notifies all waiting threads in the queue.

Monitor.Pulse notifies a thread in the waiting q

Answer 1

A Monitor has two queues: the waiting queue and the ready queue. In the absence of Wait and Pulse, all threads that try to acquire the lock go into the ready queue. When the lock becomes available, one thread from the ready queue will acquire it.

When a thread acquires the lock and then does a Wait, that thread goes into the waiting queue. It's waiting for a Pulse or PulseAll, and will remain in the waiting queue until it receives a Pulse, even if other threads from the ready queue acquire and release the lock.

Pulse moves one thread from the waiting queue to the ready queue. PulseAll moves ALL threads from the waiting queue to the ready queue.

The key here is that threads in the waiting queue can never acquire the lock. They are waiting for a pulse to move them back to the ready queue so that they can acquire the lock when it becomes available.

There's a reasonably good discussion of Wait and Pulse--at least a bit to get you started--here.

Answer 2

Use PulseAll when you want to wake up multiple threads, because the condition they're waiting for may now be fulfilled for more than one thread. (Waiting is almost always associated with a condition - you should usually be testing that condition in a while loop.)

Use Pulse when you only want to wake up one thread, because only one thread will actually be able to do useful work.

To give two analogies:

Imagine you've got a single printer. Only one person can use it at a time, so if you're got a lot of people waiting, you send them all to sleep - but you only wake one person up when the printer becomes free. This mirrors the use of Pulse.

Now imagine you run a shop. While you're closed, customers wait outside the shop. When you open the shop, you don't just want to wake up one customer - they can all come in now. This mirrors the use of PulseAll.