debugging - How do you log all garbage collection events in CLR/.Net? -

I'm looking for the same thing as java -verbose: gc or for any device or code snippet Ideally, it will be something that I can run in an unrestricted fashion in a service and log everything in a file to get information. My use is converting the long-running service to JC's motivated latency.

.NET GC profile for non-judiciousness You have some options, you can use either Or some profiler (Skatech Memory Profiler has a good command line tool that allows you to collect CLR profiling data in the production environment - other NAT profiles probably expose such a feature).

I think the display counter is the least aggressive way, but they do not give you detailed information on the GC works - however you can see how many collections have been made. You can use Perfman, Typref or PowerHail to collect this information (how many generations spent in your generation) in GC along with how many times your process was spent (I used to use Perf counter once Various methods were given so that you can see):

ETW Event Provide more information on the internal functioning of GC you can manually configure the ETW provider (Example For use by Logan or Experf) or using an excellent tool (as Mark said in a comment). If you are interested only in GC event, check the gc only checkbox in the collect window:

CRR is a big episode of dedicated Defrag tool for GC Profiling (Part 4) :, I recommend you PerfView Documentation PerfView is really a powerful tool for checking the parts and it lets you analyze NAT heap And also allows you to compare memory snapshots.

The last option (which is using a Memory Profiler ) is probably the most aggressive of three methods, but sometimes you can give more details on the GC (Especially when you want to analyze the object graph) I can not think of any good free GC Memory Profiler so you probably have to pay to get one of those tools. I have some experience with SciTech Memory Profiler (this is very good and, as I said earlier, they allow you to collect data about production). I also tried Visual Studio Memory Profile - it's not bad, but Cytec is less powerful than one - and at the end, JetBeen and Redgate also sell memory profiles that are well aware. Compared with NET developers and possibly Sytec.