Threading concept

Generally speaking, running many threads don't cause your application to run any faster. Actually, running many threads SLOWS down your application, because processor has to switch from thread to thread. Why to use threads then? Because it makes it possible to do many things "at the same time". In some cases, threads can make your application do it's job faster. If you have many jobs you have to do, and each of these jobs causes processor to idle most of the time, then it is beneficial to start these jobs at the same time, so processor can be idling for all the jobs "at the same time" :) "at the same time" in quotes because on processor can do only one job at any time, but using context-switching technique it can switch from job to another so fast that it SEEMS to do many thigs at the same time.

The concept of Threading is not so easy and cannot be explained in a few sentences. I made this experience too, I also had general Threading questions which weren't answered because of complexity. And I also found nothing in the internet. So I bought a very good book about Threading which I can commend, but it's for Visual Basic.NET (but maybe its available in C# too, otherwise its not so hard to translate). It has a section which treats exactly your problem. It's from WROX(www.wrox.com) and it's called "Visual Basic .NET Threading Handbook". I bought a second-hand one which costs me about 12 EUR, and its worth every cent of it.