How to use thread pool

Question

0.00/5 (No votes)

See more:

Hello Experts

In my application there is a method named 'saveOutput'.
This Method will not execute very fast.
Also this method is in a loop (Will execute many times)
So I thought thread pool will be a good solution.

But I have never used thread pool.

all suggestion will be regard.

Thank you.

Posted 17-Dec-13 10:13am

Meysam Toluie

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)

Ron Beyer · Answer 1 · 2013-12-17T10:25:00

Solution 1

As a beginner, I would avoid ThreadPool in favor of BackgroundWorker[^]. The link has a good example of how to use it at the bottom of the page.

Posted 17-Dec-13 10:25am

Ron Beyer

Comments

Meysam Toluie 18-Dec-13 23:54pm

I am kind of beginner but I think starting lots of threads will not helping me even with BackgroundWorker. In Addition I had experience with BackgroundWorker.

Garth J Lancaster · Answer 2 · 2013-12-17T10:39:00

In addition to Ron's comments, the end solution really depends on what you want/need to do with the output data - I'd think very carefully about the end-to-end problem first, without necessarily jumping into 'this must be threaded' etc

For example - what if you were inserting the output data into (and I'll pick the example deliberatly) a sqlite database ? You could have many threads trying to insert - which likely isnt going to work given the nature of sqlite - so, you might need a work/output 'shared' queue in the middle and a single processor that extracts an item of output from the queue and saves it to sqlite

Do you get what Im saying ?

obviously, if you're going to dump the output to a file, your problems are 'easier', but, what about a file-name - what if your filenameing convention doesnt give you a unique file, even if you get a temp file name from the system, based on a guid, what are you going to do ?

'g'