Most of the time, your computer’s CPU is sitting idle. Paul Kimmel shows how easy it is to use multithreading with the new BackgroundWorker component in .NET 2.0, so you can stop your bored gadgetry from wasting all that idle time.
Programming with the BackgroundWorker Component in .NET 2.0
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Then when we actually use software that keeps our processors busy your software will bogg us down – nice
I’m a software developer and while I’m working I have a lot of stuff open and going such as tests, my IDE, internet, etc. My processor is almost always between 80% and 100% use. Purposefully bloating software and making it use up (in my case) precious CPU cycles does not seem like a good iea.
WTF? You’re not really a software developer are you?
Then when we actually use software that keeps our processors busy your software will bogg us down – nice
This is *not* about adding more bloat to software. Multithreading is extremely useful for maximizing throughput on servers and responsiveness on clients. If your client-side application is 100% single threaded, your GUI repainting would be blocked by HD access, which would make your application appear very slow and unprofessional. On servers, you would not be able to make the most out of your 512 processing cores without multithreading.
Ok I admit I did not read the article – just read the summary and thought they were figuring most people have idle time so go ahead and eye candy up your apps (saw Background and figured it meant background images in your apps) – my mistake
Edited 2006-04-10 05:07
I don’t even think you read the summary. It clearly says “multithreading with the new BackgroundWorker component”.
I didn’t read the article either because I already know how to use the .Net 2.0 BackgroundWorker component.
You gotta love it when an idiot comments on articles they don’t read…
Yes I’m a /.er
Who told you that an extra threath would consume 80 to 100% of the CPU?
Threats are you friends if you know how to use them well.
Threats or threads? I suppose both are effective given the right circumstances.
Nope.
http://boinc.berkeley.edu/
You can participate in more than one project, and you control how much of your computing power goes to each project. If you participate in several projects, your computer will be kept busy even when one project has no work.
It’s missing the Else-clause, shouldn’t it be something like:
Private Sub ProgressUpdater(ByVal percent As Integer)
If (InvokeRequired) Then
Invoke(New Updater(AddressOf ProgressUpdater), percent)
Else
ProgressBar1.Value = percent
End If
End Sub
I just commented on the article saying this, and noting that ProgressUpdater is run on the UI thread so the bug is never encountered