BackgroundWorker

Question

Hello I've been reading and examining few sample solutions on backgroundworkers. Thus far the examples I found uses only one instance for a background worker thread. For example the progressbar examples in many sites where it loops thru thousands of times so that it can be canceled. My question is in my current project I have about 20 methods that are used to fetch different types of data. Therefore should I create 20 different instances of the BackGroundWorkers? (One for each method). I don't think it's efficient to do that am I right? Thanks

Sam Hobbs · Answer

I am not an expert in threads but I think that the Thread class and other classes in the System.Threading namespace is more appropriate for advanced use. Even though I am not an expert I think experts would say it depends on what your requiements are. Logically it makes sense to use as many threads as there are processor cores. One criteria is whether the threads will have actual work to do or do they spend time waiting. If the latter then look at the ThreadPool Class in the System.Threading namespace.