• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Memory Ballooning & SQL Server

jenuster

Limp Gawd
Joined
Mar 8, 2011
Messages
154
I've noticed that my SQL servers have a high Memory Balloon rate but the memory swap is very low. Can I safely assume, that this is due to the nature of SQL servers as it tries to grab as memory as you allocate it?
 
You shouldn't be ballooning unless the host is overcommitted on memory and is having to go through reclamation techniques outside of just TPS. Memory swap is a last resort the host will take to reclaim memory and you really, never want to see that. Your partially correct though in you assumption about why you might see ballooning more on a SQL server compared to others. ESX(i) will try and reclaim memory based on the idle memory tax, so VMs with much more static non changing memory are going to balloon more.
 
SQL will use whatever memory it thinks it has for caching which may cause the vSphere box to run low sooner than it should which is why it's using the balloon driver. Normal expected behavior. Since it's just caching on the SQL box it'll give that memory back when requested..which is why you see high ballooning but no real swapping. If you want to guarantee the SQL box can cache a lot you reserve the memory.
 
Or you could use a combination of limiting the amount of memory SQL can use along with reserving memory.
 
Back
Top