ThreadPool vs Thread - Multithreaded TCP Server?

Question

.NET

Hi all!
It is necessary to implement a multi-threaded TCP server (load ~ 10 thousand computers, each sends a request to the server once every 1 second). When a request is received from the client, the server processes it, makes a couple of requests to the database and sends a response to the client. What is better to use in this case: ThreadPool or Thread? I tried to emulate the work of the server - I created a method that simply "sleeps" for 3 seconds and displays the thread number. I performed this method in two ways - through the ThreadPool and through the Thread. The second way turned out to be faster. But how are things in reality - which will be faster?

Answer 1

Of course Pool, and here's why: https://en.wikipedia.org/wiki/C10k_problem Article: www.kegel.com/c10k.html

Answer 2

With this approach, you should already consider the IOCP model ( I / O Completion Ports )

Answer 3

Using thread in its pure form, you will have to control a lot of nuances with your hands, when in TPL it's all done for you. It is recommended to use TPL.