[Mono-list] ThreadPool threads bound to a single CPU
glen.a.ford at gmail.com
Mon Nov 26 10:36:06 EST 2007
I found this seems to be a problem under extreme load when trying to
start new threads - they are delayed by such a long time that it just
appears that way.
On Nov 23, 2007 2:06 PM, Glen Ford <glen.a.ford at gmail.com> wrote:
> I have written some test code and found that using a ThreadPool seems
> to bind all those threads to the same CPU - however if I create
> threads using parametrised thread start then they are not bound to one
> cpu but evenly spread.
> This is an issue for me as I am using a remoting service and its
> internal use of thread pool means that I am not using all the CPU's in
> my system and becoming CPU bound.
> Is this expected behaviour?
More information about the Mono-list