johanswa wrote:
PMEM/MB = 2031 vmk
Memory overhead = 1.2GB
So all overhead = 3.9GB.
Now is starting to makes sense. Was cutting it way to close, didnt know about the PMEM/MB vmk value.
Well, we are struggling with SQL performance problems, and SQL prefers a memory reservation, even though ballooning wont take please since there is only one VM on the host?
Now is starting to makes sense. Was cutting it way to close, didnt know about the PMEM/MB vmk value.SQL prefers a memory reservation - Where did you get this idea from? Have you had Microsoft or someone who is an expert in SQL performance take a look at your environment? Keep in mind that just because "Task Manager" says sqlservr.exe is consuming, say 99GB of memory, doesn't mean that it is actually *using* that much memory... it is going to claim at a minimum what the SQL admin set as the minimum memory for the instance, and usually will grab much more, if it is available, for buffer space (call it cache for sake of discussion). When Windows encounters memory pressure, SQL will give some of that memory back.
I agree with jrmunday that you need to consider looking at your I/O. You might have some tweaks either in your storage system, or maybe you have an unoptimized query, or bad application code, or some indexes that need to be created, or something else that causes more I/O than necessary. Managing SQL performance is a complex undertaking that requires expertise from several IS diciplines to handle, at times.