aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/ThirdParty/SmartThreadPool/STPStartInfo.cs
diff options
context:
space:
mode:
authorDr Scofield2009-06-25 08:17:37 +0000
committerDr Scofield2009-06-25 08:17:37 +0000
commit98ea70644abd9c51c5534b416a12ef56c8ead07e (patch)
tree9ebd6555a63d77bd22f38e102c19aba65454a86c /ThirdParty/SmartThreadPool/STPStartInfo.cs
parentcosmetic change (diff)
downloadopensim-SC_OLD-98ea70644abd9c51c5534b416a12ef56c8ead07e.zip
opensim-SC_OLD-98ea70644abd9c51c5534b416a12ef56c8ead07e.tar.gz
opensim-SC_OLD-98ea70644abd9c51c5534b416a12ef56c8ead07e.tar.bz2
opensim-SC_OLD-98ea70644abd9c51c5534b416a12ef56c8ead07e.tar.xz
From: Alan Webb <alan_webb@us.ibm.com>
After noticing on several occasions that the thread counts we see when running OpenSIm were bordering on the astronomical I decided to seriously investigate. After much poking I discovered that the problem is actually very simple. The XEngine secition of the example ini says that the timeout for an iden thread is in seconds, and an example value of 60 is specified. In fact, this is actually resulting in a 60mS idle timeout, which is not normally enough for a smart thread to survive. I have added a multiplier to the XEngine constructor so that the number now matches the published behavior.
Diffstat (limited to 'ThirdParty/SmartThreadPool/STPStartInfo.cs')
0 files changed, 0 insertions, 0 deletions