Witango-Talk: threadPoolsize - 5.0.1.065

[Chuck Lockwood]

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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ LockData Technologies, Inc.                  309 Main Avenue, Hawley, Pa 18428          570-226-7340 ~ Fax: 570-226-7341    [EMAIL PROTECTED] ~ www.lockdata.com                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf