What if BackgroundWorker control used massively?

Question

5.00/5 (1 vote)

See more:

I'm being afraid if a mass usage of BackgroundWorker control in a C# program will make the program slow and poorly responsible. So tell me if there is any such or any other problem if BackgroundWorker control used massively?

Posted 3-Nov-11 2:28am

iKrshnan

Add a Solution

Comments

BillWoodruff 3-Nov-11 22:24pm

You have two excellent answers here; my one comment is that: to really reply to your question you need to explain what "massively" and "mass usage" mean.

"Mass usage" could mean using a lot of different threads via BackGroundWorker(s). "Massively" could mean using one BackGroundWorker that made heavy demand on CPU bandwidth.

Please specify the scenario.

[no name] 4-Nov-11 3:16am

Its "Mass usage" scenario from your comment. Otherwise, if a BGW that made heavy demand on CPU bandwidth, it will make the program slow indeed.

2 solutions

Solution 2

The main reason a background worker would have a bad effect on performance would be too much communication between the background process and the main thread (for ex. calling ReportProgress too often or locking objects too much).

Posted 3-Nov-11 15:31pm

Philippe Mori

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)

BobJanova · Accepted Answer · 2011-11-03T02:37:00

Solution 1

I believe that BackgroundWorkers (and .Net 4 Tasks) use a thread pool, and will make appropriate use of threads. Of course, if you're trying to do too much at once the program will become slow – that's true however you divide up the work. But I don't think BackgroundWorkers will give you massive overhead problems.

Posted 3-Nov-11 2:37am

BobJanova

Comments

[no name] 3-Nov-11 8:39am

Agreed. There is a point when adding more threads doesn't give you any returns and starts to have negative impacts on performance

DaveyM69 3-Nov-11 10:39am

Correct - 5.