[Mono-dev] ThreadPool threads bound to a single CPU

[Glen Ford]

Hi,


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?


Regards,


Glen