-
Notifications
You must be signed in to change notification settings - Fork 266
Add ASP.NET Core memory pool metrics #2533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
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]