John,
Actually depends on which version the host process specifies to the shim loader, but
if Workstation is default if nothing is specified.
I don't know the exact answer for ASP.NET, but my guess is that since it's a
server-side process then logically the Server GC is specified explictly when loading
CLR via CorBindToRuntimeEx API. The only caveat to this is the number of CPUs on the
machine in question; if there's only one then the Workstation GC will always be used,
even when Server GC is specified, because on single proc. Workstation outperforms
Server.
For more information on the inner workings, I've found this article to be really
helpful:
http://msdn.microsoft.com/msdnmag/issues/01/03/clr/default.aspx
Hope this helps.
Mike
-----Original Message-----
From: John Crim [mailto:[EMAIL PROTECTED]
Sent: Mon 6/30/2003 2:46 AM
To: [EMAIL PROTECTED]
Cc:
Subject: [ADVANCED-DOTNET] ASP COM object using Interop -> which GC is used?
It certainly seems preferable that .NET components, used in ASP applications
via COM Interop, would use the Server GC instead of the Workstation GC.
For background, many articles discuss that the Server Garbage Collector is
appropriate for high-throughput use, and the Workstation Garbage Collector
is meant for single user apps with a UI.
Can anyone tell me which GC is used? If it's the workstation GC, is there a
way to specify that the Server GC be used instead?
Thanks in advance,
John Crim
WebRelevance
[EMAIL PROTECTED]
