C# threading problem

i am trying to simplify problem as follows,

1. i have around 100+ files that i would like to read and then process the data
2. For which i maintain array of file names and location
3. I spawn threads to do the job of reading files.

Now my problem is i would like to make sure that only 5 t开发者_运维技巧hreads are spawn at a time as starting 100 + threads is not good idea at all.

So please tell me what approach i should use to ensure that the only 5 threads are working at time and as soon as even one of them is done new one can be started.

Thanks all,

I vote for the task parallel library / Rx (included in .NET 4.0, but downloadable for 3.5):

        var options = new ParallelOptions();
        options.MaxDegreeOfParallelism = 5;

        Parallel.ForEach(GetListOFiles(), options, (file) =>
        {
             DoStuffWithFile(file);
        });

Note that this will use up to 5 threads, but I've seen it use less.

You should take a look at the

system.threading.threadpool.setmaxthreads

Split your file list into 5 equal size lists. Then start five threads, and pass each a separate smaller list via ParameterizedThreadStart.

However, since the work is almost entirely I/O bound, this process is not likely to benefit from threading.

Though this might not answer your question directly, but it seems that a producer-consumer design would fit your needs. Also, this might help.

I usually do this approach:

Declare a shared integer variable to denote number of working threads. When a job is assigned to a thread (simply queue the job into ThreadPool), increase the value. When a thread completes the job, decrease the value.

Make sure of decrement or increment of the integer value as atomic.

In the job dispatcher, fetch a job and assign to a thread only if number of working threads is less than the maximum value. Otherwise, wait for a signal (which will be triggered by a working thread completing a job). If you want event simpler, let the dispatcher simply do empty loop to wait.

The good point is that the maximum value is configurable, and it takes the advantage of the built-in ThreadPool. Writing a consumer/producer model to solve such a small problem is costly.

Do your processing through ThreadPool, then setMaxThreads

http://msdn.microsoft.com/en-us/library/system.threading.threadpool.setmaxthreads.aspx