Regarding Threads and Consideration of Threads in .Net

Question

0.00/5 (No votes)

See more:

Actually I got some 1000 individual processes to be executed independently. Each process will take 2 to 3 mins to complete. I want to execute all the process in Thread mode. My question is how many Threads can I use. In other words, how can I compute an optimum combination of no. of Threads and memory management to execute all these 1000 processes in a minimal time?

Posted 10-May-13 9:31am

chenthil28

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-05-10T11:23:00

For the overall throughput, practically, it makes little sense to use more threads then CPU cores. Let's assume your all your other process are in the wait mode and don't take CPU resources. All correctly designed UI applications are like that. It means that your threads take all the time. Now the question is: do they use 1) each other, 2) external resources, such as network or external devices? If some of the above is correct, threading can really help, because, for example, the communication can be a bottleneck and then you can use several channels. In other works, parallel computing can help only if your have resources which can be used in parallel. Also, (case #1), the threading is dictated by the poor logic; for example, the UI should remain responsive anytime.

If you don't have anything like that, then number of threads should be the same as the number of cores. If number of cores is low (and apparently, if you have only 1 core), executing such independent tasks in more then one thread can even slow down the overall execution. Why? Because threading has some performance overhead.

—SA

Ron Beyer · Answer 2 · 2013-05-10T09:37:00

The number of threads is limited by the runtime or in the case of ASP, IIS. Finding a balance of concurrent execution versus wait times is a matter of academics, and finding what works best for you is designing a framework that you can easily change the number of concurrent threads and increase that value until you see a performance drop. This depends heavily on the processor architecture and other overhead on the system at any given time, so it's really not as simple as giving a number.

Regarding Threads and Consideration of Threads in .Net

2 solutions

Solution 2

Solution 1

Add your solution here

Preview 0