Task managed ID question

Question

5.00/5 (1 vote)

See more:

Within a Task execution does the Thread.CurrentThread.ManagedThreadId stay the same, given that the Task are executed within a Threadpool and are recycled?

Posted 20-Jun-12 6:55am

Mehdi Gholam

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mehdi Gholam · Accepted Answer · 2012-06-20T22:25:00

The following seems to work ok :

C#

public static void Main(string[] args)
{
    for (int i = 0; i < 1000000; i++)
        Task.Factory.StartNew(() => work());
}

private static void work()
{
    int i = Thread.CurrentThread.ManagedThreadId;
    dosomework(i,0);
}

private static void dosomework(int i, int c)
{
    if (c == 3) return;
    Thread.Sleep(1);
    int j = Thread.CurrentThread.ManagedThreadId;
    if (i != j)
        throw new Exception("failed");
    dosomework(i,++c);
}

So as far as this test goes it seems that the call chain is executed on a single Thread.

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-06-20T08:12:00

To best of my knowledge, System.Threading.Tasks.Task is implemented by automatic mapping on threads, and we know that on Windows .NET threads are implemented on the base of OS threads (not fibers or some .NET specific mechanism). That said, the system should not guarantee that every time a task is executing its time slice, the current thread being executed is the same in all cases.

You see, you can easily try to confirm it by experiment, but the problem is: if you observe that a current thread is sometimes different, it would confirm it, but if you observe that the current thread is the same for the same task, it would not prove anything.

[EDIT]

Indirectly, what I say is confirmed by Microsoft documentation: http://www.codeproject.com/script/Answers/Post.aspx?aid=407532[^]:

Behind the scenes, tasks are queued to the ThreadPool, which has been enhanced with algorithms (like hill-climbing) that determine and adjust to the number of threads that maximizes throughput. This makes tasks relatively lightweight, and you can create many of them to enable fine-grained parallelism. To complement this, widely-known work-stealing algorithms are employed to provide load-balancing.

From all this documentation article, I don't see a reason why a task instance should be guaranteed to run by the same thread. I think it would be safest to say: this is implementation-dependent.

[END EDIT]

If you go so far to try it out, of find out exact documentation explicitly explaining this matter, please notify me by commenting on this answer.

—SA

Task managed ID question

2 solutions

Solution 2

Solution 1

Add your solution here

Preview 0