What is the Maximum Theread in a process possible under .Net envoi

[Manish]

Hi !
I got the answer of this question in a different group i.e. windows/server ,
i am quite satisfied with the answer that seem for windows programing (32
bit/64 bit native applications (unmanaged), refer the below link

http://blogs.technet.com/markrussinovich/archive/2009/07/08/3261309.aspx

Q1. What is the Maximum Theread in a process possible under .Net envoirnment
(Memory mangement etc) ?

Waiting for your reply

Regards
Manish

 

[Peter Duniho]

Hi !
I got the answer of this question in a different group i.e. windows/server ,
i am quite satisfied with the answer that seem for windows programing (32
bit/64 bit native applications (unmanaged), refer the below link

http://blogs.technet.com/markrussinovich/archive/2009/07/08/3261309.aspx

Q1. What is the Maximum Theread in a process possible under .Net envoirnment
(Memory mangement etc) ?

For now, the managed answer is roughly the same as the unmanaged answer,
because most of the cost of a thread in managed code is the unmanaged
thread underlying it.

If I recall correctly, one version of .NET (a server version, I think)
implements threads using fibers, which are lighter weight and so would
allow more threads for a given OS version.

Noting, of course, that in managed or unmanaged code if you getting
anywhere close to the actual maximum number, you've really messed up
your code. Even on a 32-bit, non-fiber implementation the maximum is a
couple thousand, which far exceeds the number of threads needed to gain
any performance benefit and any theoretical architectural benefit will
be negated by the performance overhead of having to deal with thousands
of threads.

Pete