Consider using new GetGCMemoryInfo API when targeting net5.0+

[rwkarg]

This is extended information that may be able to pull GC info in a way that is less performance intensive.

Blog Post: https://devblogs.microsoft.com/dotnet/the-updated-getgcmemoryinfo-api-in-net-5-0-and-how-it-can-help-you/

[djluck]

So I have looked at this API and it's something I might consider for v4 but at the moment I'm leaning away from it:

• it isn't clear how this API can be used to get information on all GC collections (do you endlessly call this method in a loop?) as it just seems to return metrics on the last collection that occurred
• the overhead of listening to Info level GC events is actually quite low

[sywhang]

That API isn't meant to be used for getting info on all GC collections - for that using EventListener as this library currently does is the current recommendation.

GCMemoryInfo API can help you though, if you're interested in sampling. This is the backing API for some of the runtime GC counters published by CoreCLR.