Re: Thread Pool AvailableThreads is always 25
anonymous_at_discussions.microsoft.com
Date: 05/06/04
- Next message: Sylvain Ross: "Collection filling weird behavor"
- Previous message: David Browne: "Re: Thread Pool AvailableThreads is always 25"
- In reply to: David Browne: "Re: Thread Pool AvailableThreads is always 25"
- Next in thread: Chris Mullins: "Re: Thread Pool AvailableThreads is always 25"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 6 May 2004 15:06:58 -0700
>Another thing is that if your listener is not relying on
ThreadPool threads
>to accept connections, then even if you have all 25
ThreadPool threads busy,
>you will still be able to accept new connections!
Thanks David, I'll try it. That looks like it will solve
my connection refusal problem.
Why do you suppose the available threads is showing a full
25 the entire time? My stress test program is a simple
client that sends the server a random number and the
server returns back the next sequential number. Each
client does this 100 times and closes.
If I fire off 1000 clients in 10 ms intervals and watch
the available worker thread count on the server, it stays
25 but my client connections are getting slower responses
from the server the more clients I add.
Seems to me like the available threads would start
decreasing in response to the high demand.
- Next message: Sylvain Ross: "Collection filling weird behavor"
- Previous message: David Browne: "Re: Thread Pool AvailableThreads is always 25"
- In reply to: David Browne: "Re: Thread Pool AvailableThreads is always 25"
- Next in thread: Chris Mullins: "Re: Thread Pool AvailableThreads is always 25"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|