I need clarification on ThreadPool and Managed Thread(s) C#

Question

2.00/5 (1 vote)

See more:

From my limited understanding ThreadPool creates the optimal number of threads and queues incoming "work" if the the optimal number of threads have been created and are in use (working)...

Isn't this the exact same thing as creating a multiThreaded consumer-producer queue? If so what's the need/purpose of creating a managed synchronized thread w/ a queue holding the work/task "IF" I can use a ThreadPool and accomplish the same thing?

Thanks in advance,
-DA

Posted 22-Dec-11 12:52pm

d.allen101

Add a Solution

1 solution

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-12-22T13:24:00

No, of course these are absolutely different things. Thread pool is just the automated thread re-use mechanism. As to the queues used in thread synchronization, it does not really matter how the threads were obtained. Isn't that obvious? Threads are threads; when you set up the thread's properties and are using it already, it works in exact same way, not matter the way you obtained it.

The queuing mechanism and inter-thread invocation is explained in detail in my Tips & Tricks article "Simple Blocking Queue for Thread Communication and Inter-thread Invocation"[^], complete with source code and usage sample. One interesting case is using delegate instances as queue elements, which makes the mechanism of invocation extremely flexible, similar the invocation mechanism used with UI threads with WPF and System.Windows.Forms.

—SA