|
My own ‘reasonable limit’ for the
threadpool is 15 – the default. I started with 10, and saw that there
were times when 11-15 threads would be used by my users, so I increased it to
15. I suspect that should my sites get busier, I would need to go to 20. I
would not go above 25, but rather look to adding more servers/services. Typically my max threads
is around 10 now. I have one service at Robert -----Original Message----- I and a few esteemed colleagues were
stress testing an application and found that we could hang the server if we had
the threadPoolSize set high and did enough large database queries at once to
cause most or all of the threads to be used. However, if we lowered the
threadPoolSize, Witango queued the additional requests instead of trying to run
them all concurrently and everything finished fine. In other words, it
worked exactly as the documentation states. The question becomes, how do you
intelligently set the threadPoolSize based on server memory and processor power
without “guessing” at a reasonable upper limit? Thoughts? Chuck Lockwood ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
- Witango-Talk: threadPoolsize - 5.0.1.065 Chuck Lockwood
- Re: Witango-Talk: threadPoolsize - 5.0.1.065 Robert Shubert
- Re: Witango-Talk: threadPoolsize - 5.0.1.065 Alan Wolfe
- RE: Witango-Talk: threadPoolsize - 5.0.1.065 Robert Shubert
- RE: Witango-Talk: threadPoolsize - 5.0.1.065 Bill Downall
- RE: Witango-Talk: threadPoolsize - 5.0.1.065 Robert Shubert
- Re: Witango-Talk: threadPoolsize - 5.0.1.0... John McGowan
- RE: Witango-Talk: threadPoolsize - 5.... Robert Shubert
- Re: Witango-Talk: threadPoolsize ... John McGowan
