Understanding the .NET Thread Pool
In the previous section you saw how simple it is to create and run a new thread. When you have one or two threads, things are also easy for performance. But if you decide to split a process or an application across lots of concurrent threads, the previous approach can cause performance and resources overhead. So you should manually search for the best configuration to fine-tune system resources consumption with your threads. Your application can run on different configurations in terms of available memory, processors, and general resources, so it is difficult to predict how many threads you can launch concurrently on target machines without affecting performance and causing overhead. Fortunately the .NET Framework ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access