sp_BlitzFirst: add analysis of sys.dm_os_memory_clerks usage #3490
Labels
Someday Maybe
Features that would be interesting to build if we had extra development time
sp_BlitzFirst
Is your feature request related to a problem? Please describe.
A few different related issues:
Grabbing a screenshot of with In-Memory OLTP consuming 4.3GB (memoryclerk_xtp, db_id_2) just for reference, not that 4.3GB is a problem:
![Screenshot 2024-04-15 at 10 46 21 AM](https://private-user-images.githubusercontent.com/245462/322524469-6fa5a8ed-1b27-4fcf-a2ef-94dd362bcff5.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk5MTg4NzAsIm5iZiI6MTcxOTkxODU3MCwicGF0aCI6Ii8yNDU0NjIvMzIyNTI0NDY5LTZmYTVhOGVkLTFiMjctNGZjZi1hMmVmLTk0ZGQzNjJiY2ZmNS5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwMlQxMTA5MzBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zY2ExZWQxNmQ3M2E2M2Y0YTg2OWJiNWM4YmUzZGFjNGIwOWI2Zjc3MmExMWY5ZmRlODI3NzE5NjZmODU4MTE3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.5FeyLW_i8qriSY7ju7xfVFgbaglzcdDWR4lklOaeYnI)
Describe the solution you'd like
We've already got one check on sys.dm_os_memory_clerks for the user and token perm cache issue, but I'd like to expand that to a few other situations.
Describe alternatives you've considered
Drinking. I'm still tempted by that alternative.
Are you ready to build the code for the feature?
Yes.
The text was updated successfully, but these errors were encountered: