Thundering herd problem
In computer science, the thundering herd problem occurs when a large number of processes or threads waiting for an event are awoken when that event occurs, but only one process is able to handle the event. After all the processes wake up, they will start to handle the event, but only one will win. All processes will compete for resources, possibly freezing the computer, until the herd is calmed down again.
The Linux-kernel will serialize responses for requests to a single file descriptor, so only one thread (process) is woken up.
Similarly in Microsoft Windows, I/O completion ports can mitigate the thundering herd problem, as they can be configured such that only one of the threads waiting on the completion port is woken up when an event occurs.
In systems which rely on a backoff mechanism (e.g. exponential backoff), the clients will retry failed calls, by waiting a specific amount of time between consecutive retries. In order to avoid the thundering herd problem, jitter can be introduced, in order to break the synchronization across the clients thereby avoiding collisions. In this approach, randomness is added to the wait intervals between retries, so that clients are no longer synchronized.
- Process management (computing)
- Lock convoy
- Sleeping barber problem
- TCP global synchronization
- Cache stampede
- "Thundering Herd Problem". The Jargon File (version 4.4.7). Retrieved 9 July 2019.
- Howsden, Mike. "Mitigating the Thundering Herd Problem at PBS with NGINX". NGINX. Retrieved 9 July 2019.
- "Does the Thundering Herd Problem exist on Linux anymore". stackoverflow.com. Retrieved 2019-07-09.
- "IO Completion Ports — Matt Godbolt's blog". xania.org. Retrieved 2019-01-23.