09-10-2025, 09:29 PM
Hello,
I have a TIdTcpServer project with many clients that have permanent connections. At the moment I am having 2300 concurrent connections (=2300 threads) all the time and I am running into performance problems. The machine I am running the server application on is a Windows Server 2019 with 8 cores and 24 GB of RAM.
I suspect the application starts running slow because of the thread scheduling of the operating system.
I have been reading about the IdSchedulerOfThreadPool that would use a thread pool instead of 1 thread per connection, but I also read something that contradicts that a IdSchedulerOfThreadPool would help.
What is the best I can do to handle that many concurrent connections?
Vincent
I have a TIdTcpServer project with many clients that have permanent connections. At the moment I am having 2300 concurrent connections (=2300 threads) all the time and I am running into performance problems. The machine I am running the server application on is a Windows Server 2019 with 8 cores and 24 GB of RAM.
I suspect the application starts running slow because of the thread scheduling of the operating system.
I have been reading about the IdSchedulerOfThreadPool that would use a thread pool instead of 1 thread per connection, but I also read something that contradicts that a IdSchedulerOfThreadPool would help.
What is the best I can do to handle that many concurrent connections?
Vincent