One of the big places it gets involved with is Garbage Collection
http://michaelrichardson.org/?p=7
As for spawning appdomains on different CPUs I don't believe it is possible
and I think you would actually see worse performance for this than allowing
the underlying scheduler to do its work mapping tasks to CPUs.
Cheers,
GReg
>I am trying to find additional information on how the CLR works with
>multiple
> CPUs in .net 2.0 framework. Is it enabled by default? Can I spawn multiple
> appDomains on specific CPUs or does it only relate to multithreading?
vzaffiro - 03 May 2006 14:09 GMT
So would it be safe to assume to the CLR only takes advantage of multiple
CPUs with multi-threading and GC?
> One of the big places it gets involved with is Garbage Collection
> http://michaelrichardson.org/?p=7
[quoted text clipped - 11 lines]
> > CPUs in .net 2.0 framework. Is it enabled by default? Can I spawn multiple
> > appDomains on specific CPUs or does it only relate to multithreading?
Marcus Heege - 03 May 2006 15:13 GMT
> So would it be safe to assume to the CLR only takes advantage of multiple
> CPUs with multi-threading and GC?
No. On the one hand, you can create multiple CLR threads yourselves (via
System.Threading.Thread) on the othe hane, there is a thread CLR pool that
contains threads used for asynch operations and IO operations.
vzaffiro - 03 May 2006 19:01 GMT
Thanks for your response...
Do you need to notify the CLR of multiple CPUs?
> > So would it be safe to assume to the CLR only takes advantage of multiple
> > CPUs with multi-threading and GC?
>
> No. On the one hand, you can create multiple CLR threads yourselves (via
> System.Threading.Thread) on the othe hane, there is a thread CLR pool that
> contains threads used for asynch operations and IO operations.
Greg Young - 05 May 2006 01:02 GMT
Not at all ...
> Thanks for your response...
>
[quoted text clipped - 8 lines]
>> that
>> contains threads used for asynch operations and IO operations.