Does Time.Sleep Block Goroutines?

The usage of time.Sleep raises the question of whether it hinders goroutines. The answer is affirmative.

However, the manner in which goroutines are scheduled across threads is subject to alteration with each release and can vary based on platform. It adheres to the "MPG model," which provides a conceptual understanding but is not a precise description of the scheduling algorithm.

When invoking time.Sleep, the scheduler may conclude that additional threads are unnecessary while goroutines are merely waiting. As a result, it optimizes thread utilization.

Distinction between Examples

In the first example, using time.Sleep, the scheduler creates a modest number of threads because the goroutines are dormant. In contrast, the second example employs disk I/O, which necessitates additional threads to handle the concurrent file writes.

When to Be Concerned

While it's theoretically possible to create an excessive number of kernel threads through deliberate code manipulation, it is not a common concern for developers writing regular production code. However, if you encounter an unusually high thread count, it's wise to examine your code and address any underlying issues.