<font color="blue"> <This is not a LoadRunner or PerformanceCenter issue - removed LR profile info> </font>
I performing som performance tests on a .NET application running in Windows and am getting the impression that the GC for .NET does not trigger until the physical memory is about to run out. I have tried to find information on the web on this, but have not found anything that describe exactly when the GC triggers.
Do you guys have any links to info or know when the GC triggers in .NET?
My experience with this is that it can very difficult to predict exactly when a garbage collection takes place. If you need to know when it happens, that can be monitored with perfmon.
It is possible that with the right test program and controlled environment, you could get GC to happen at the same time. In a production implementation, you are working with "self-optimizing" software that has multiple factors feeding a proprietary algorithm, so you are going to have an extremely difficult time getting the level of visibility you are looking for.
[ QUOTE ] David: The link did not describe when the GC triggers. I would like to know what criteria cause it to start. Anyone?
[/ QUOTE ]
The idea was to give you a link as a starting point so you could continue your own research. If you look at the links provided by Joe - the roots are the same. We do not generally replicate any of MSDN's work.