should expose the accumulative GC pause duration as a counter

[Maoni0]

essentially expose what's implemented in this API that @cshung is working on. this should replace the current % time in GC since last GC which is simply not a good counter. see explanation here.

[ghost]

Tagging subscribers to this area: @dotnet/gc
See info in area-owners.md if you want to be subscribed.

Issue Details

---

essentially expose what's implemented in this API that @cshung is working on. this should replace the current % time in GC since last GC which is simply not a good counter. see explanation here.

Author:	Maoni0
Assignees:	-
Labels:	area-GC-coreclr, untriaged
Milestone:	-

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

essentially expose what's implemented in this API that @cshung is working on. this should replace the current % time in GC since last GC which is simply not a good counter. see explanation here.

Author:	Maoni0
Assignees:	-
Labels:	area-Diagnostics-coreclr, area-GC-coreclr, untriaged
Milestone:	-

[Maoni0]

@tommcdon could someone from your team please add this?

[tommcdon]

@Maoni0 thanks for the suggestion! Adding @mikelle-rogers to take a look.

[joaocpaiva]

+1

Having a reliable counter to track the relative cost of GC pauses is important to identify regressions or validate improvements, as it reflects in tail latency and CPU. And for cloud services, tracking the relative cost of GC becomes paramount, especially for latency-sensitive workloads. Please prioritize this accordingly.