[Mono-list] Thread Pool issues
Gonzalo Paniagua Javier
gonzalo.mono at gmail.com
Sat Apr 3 11:55:40 EDT 2010
On Sat, 2010-04-03 at 05:31 -0800, aldus wrote:
> Gonzalo Paniagua Javier-3 [via Mono] has written:
> > MonoMaxActiveRequests docubox 0
> > MonoMaxWaitingRequests docubox 0
> > And I would remove that MONO_THREADS_PER_CPU setting. It is too
> > -Gonzalo
> Thank you Gonzalo.
> I have found the "MONO_THREADS_PER_CPU =2000" settings as a setting
> solve the Max Active Request issue on this mailing list.
> It works with 2.6.1 but not with 2.6.3.
> Now I have put this new settings on our server.
> We have two applications on the same server, the first named
> and the other named "serinfo", then I have add these settings twice
> rows for each application), that's right?
Yes. When you don't specify an application name (docubox, serinfo) the
default value is 'default'. That's why the settings you had before
didn't apply to your applications.
> Now, my new questions are:
> 1. What is the right value to use for "MONO_THREADS_PER_CPU" ?
> 2. If these new settings solve the issue, there is any need to change
> the "Threads Per Cpu" value?
The right value depends on your application, the load it gets and the
CPU/memory that you have. I would set that environment variable to the
lowest number that can handle the typical load you get.
There is a new threadpool in trunk that dynamically adjusts the number
of active threads and will make MONO_THREADS_PER_CPU obsolete (or change
More information about the Mono-list