How do Kotlin coroutines behave under thread pool saturation?

When thread pools are saturated, coroutines are queued, delayed, or suspended until threads become available.

Coroutine dispatchers rely on underlying thread pools. If all threads are busy, new coroutines are queued. This increases latency and can cause cascading delays. In extreme cases, if blocking calls dominate threads, starvation occurs. Proper separation of IO and CPU dispatchers prevents saturation collapse.