We are seeing a lot of Non-yielding scheduler errors on a SQL Server VM. Reading this link on Microsoft Docs, it's recommended we enable Lock Pages in Memory.
I do not have much experience with Lock Pages in Memory, and I've read a lot of blog posts that express caution around turning it on.
- Windows Server 2016
- SQL Server 2017 CU27
- 504 GB total RAM
- 64 cores
- 43GB page file
- Max Server Memory is set to 460 GB
- MaxDOP 16
I'm looking for advice from people with experience around Lock Pages in Memory, specifically on VMs with large memory. Or if there is another option I have not thought of?