Skip to content
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

sp_BlitzFirst: add analysis of sys.dm_os_memory_clerks usage #3490

Open
BrentOzar opened this issue Apr 15, 2024 · 1 comment
Open

sp_BlitzFirst: add analysis of sys.dm_os_memory_clerks usage #3490

BrentOzar opened this issue Apr 15, 2024 · 1 comment
Assignees

Comments

@BrentOzar
Copy link
Member

BrentOzar commented Apr 15, 2024

Is your feature request related to a problem? Please describe.
A few different related issues:

  • The plan cache, query workspace, In-Memory OLTP, or memory-optimized TempDB consumes a large amount of memory
  • The buffer pool consumes a small percentage of memory
  • Total amount of pages_kb is higher than max server memory (this one is a little tricky, and probably need to build a repro query)

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

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.

@BrentOzar BrentOzar self-assigned this Apr 15, 2024
@erikdarlingdata
Copy link
Contributor

There's a section in sp_PressureDetector that does this, and might be a good starting place if you need one. I remember being really annoyed with the amount of dynamic SQL necessary to make it compatible across older SQL Server versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants