Add ASP.NET Core memory pool metrics#2533
Conversation
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
af19518 to
3b13ed9
Compare
|
All changes have been applied. Please take another look. |
|
Is there an invariant: aspnetcore.memory_pool.pooled = aspnetcore.memory_pool.allocated - aspnetcore.memory_pool.rented - aspnetcore.memory_pool.evicted |
|
No, because rented is total. Memory could be returned and rented many times. Allocated: 50 bytes Pooled does not equal -450 bytes. One interesting piece of data is how much an application has currently leased. You can calculate the currently leased memory with this: |
3b13ed9 to
86a6839
Compare
|
Hey @JamesNK , is there any particular reason why these metrics are not documented here? |
|
Never got around to it. AI could probably copy it across quickly |
Thanks for clarifying. I was wondering if there was a chance this was actually not pushed as part of .NET 10 and that was maybe why. Good to hear that's not the case. |
Fixes #2532
Changes
Please provide a brief description of the changes here.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]