Custom thread pool

Oct 16, 2009 at 3:26 PM

TCPServer class. Why do you use a custom thread pool? What benifits does it give over the .NET thread pool.  Why do you use a thread pool thread for each request instead of just listening asynchronously and using the io thread pool?

Oct 16, 2009 at 7:01 PM
Edited Oct 16, 2009 at 7:04 PM

all my perf. test have shown that its much faster then to use the internal one.

checkout the following link:


Oct 21, 2009 at 9:09 AM

IMO the use of the first PostRequest call in the TCPServer is not necessary, you are tying up a thread pool thread for no other reason than to wait on an Async call.  If you are trying to use this thread pool as some kind of throttling solution ( again i do not think necessary) the second call to PostRequest would throttle ( ie queue requests when all threads assigned to the pool are busy).

I have not quite pinpointed the issue yet but under heavy load the server falls over and i am suspecting it may have something to do with the custom threadpool, i will let you know when i work it out.