Question

Here is a console program want 10 threads start in batch, wait 5 seconds, and stop in batch.

static void Main(string[] args)
{
    System.Threading.Tasks.Parallel.For(0, 10, (index) =>
    {
        Action<int> act = (i) =>
        {
            Console.Write("start {0} ", i);
            Thread.Sleep(5000);
        };

        act.BeginInvoke(index, OnTaskComplete, index);
    });

    Console.ReadKey();
}

static void OnTaskComplete(IAsyncResult res)
{
    Console.Write("finish {0} ", res.AsyncState);
}

but the result is not what I expected, 10 threads start one-by-one SLOWLY(around 1 second interval), even some “finish” comes out before some “start”.

when comment out Thread.Sleep, all threads start and finish in flash.

Does Thread.Sleep affect other threads? Is there anyway to make a pure idle time?

/—————————–edit—————————–

same problem also happen in:

static void Main(string[] args)
{
    System.Threading.Tasks.Parallel.For(0, 10, (index) =>
    {
        Console.Write("start {0} ", index);
        Thread.Sleep(5000);
        Console.Write("fnish {0} ", index);
    });

    Console.ReadKey();
}

———————-Edit————————

finally I found a lovely way to substitute thread.sleep

static void Main(string[] args)
{
    System.Threading.Tasks.Parallel.For(0, 10, (index) =>
    {
        Console.Write("start {0} ", index);

        var t1 = new System.Threading.Timer(new TimerCallback(MyTimerCallback), index, 5000, 0); 
    });

    Console.ReadKey();
}

static void MyTimerCallback(object o)
{
    Console.Write("Timer callbacked ");
}

Answer 1

This is by design. You are seeing the threadpool manager trying to keep a limited number of threads in the executing state. Important to ensure that your program isn’t running more threads than your machine has cpu cores. That’s inefficient, less work gets done when Windows is forced to start swapping the cores between active threads. The threadpool manager isn’t smart enough to know that the thread is sleeping and not actually performing any work.

On a dual-core machine, you’ll see the first 2 threads starting right away. Then additional threads are allowed to run, one by one with a one second interval when the thread manager notices that the active threads are not making any progress and are probably blocked. The order in which threads are released and execute the Console.Write() call is not deterministic.

This is an artificial test of course, real threads don’t sleep. If you have threads that block for a long time, waiting for an I/O request to complete for example then using threadpool threads (tasks) is not the best solution.