Wading through all of the SQL Server memory-related perfmon counters to understand how they related to each other took me a really long time. Time-series graphs that show the relationship help me tremendously, and when I started trying to account for SQL Server memory years ago I couldn’t find any. So I started to blog some time-series graphs, under the theory that either my understanding was correct and my graphs would be helpful to someone… or they’d be wrong and someone would correct me.
Well… its been about 5 years and my graphs haven’t generated too much discussion, but they’ve really helped me 😀😀😀
Perfmon: SQL Server Database pages + Stolen pages + Free pages = Total pages
Working with SQL Server 2016 and some demanding ColumnStore batch mode workloads, I began to see suspicious numbers, and graphs that didn’t make sense to me. Today I got pretty close to figuring it out so I wanted to share what I’ve learned.
The following graphs are from a 4×10 physical server running Windows and SQL Server. Four sockets, 4 NUMA nodes.
For bonus points, Lonny traces down a problem where expectations aren’t meeting reality.