Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Add Buffer Cache Hit Ratio / Checkpoint Pages per Sec #31
Conversation
|
Thanks for contributing. And as usual, apologies for how long it took. |
|
Hello, buffer cache hit ratio is not correct here, sorry. The value must be calculated from the base value. Example : https://github.com/rudi-bruchez/tsql-scripts/blob/c920c631c47560a8575ceae0ef135dd9bb2b913b/diagnostics/performance-counters.sql |
* add buffer cache hit ratio to default mssql metrics * add checkpoint pages per second
From https://www.datadoghq.com/blog/sql-server-monitoring/:
Buffer cache hit ratio
The buffer cache hit ratio measures how often the buffer manager can pull pages from the buffer cache versus how often it has to read a page from disk. The larger the buffer cache, the more likely it is that SQL Server can find its desired pages within memory. SQL Server calculates the size of the buffer cache automatically, based on various system resources such as physical memory. If your buffer cache hit ratio is too low, one solution is to see if you can increase the size of the buffer cache by allocating more system memory.
Checkpoint pages/sec
During a checkpoint, the buffer manager writes all dirty pages to disk. As we’ve seen, during lazy writing, SQL Server only writes some pages, letting the buffer manager make room in the buffer cache for new pages. By monitoring the rate at which pages are moved from the buffer cache to disk specifically during checkpoints, you can start to determine whether to add system resources (to create a larger buffer cache) or reconfigure your checkpoints (e.g., by specifying a recovery time) as you work to optimize the buffer manager.