This VMware status shows the rate at which memory is being swapped in from disk or out to disk. A non-zero number represents a lack of memory and a clear indication that SQL Server or Oracle VM performance is suffering as a result.
Background
Initially when VMware host memory over-commit happens, memory will be swapped out. You may see memory contention resulting from memory being swapped in and out for a period of time. When memory pressure subsides, memory will be swapped back in. Because memory is swapped without regard to the actual portions being used, memory swapping can cause serious SQL Server or Oracle VM performance issues.
Solutions
You must first determine whether or not the memory was swapped because of too many SQL Server or Oracle VMs being powered at once. Check the log files from guest OSes of Oracle or SQL Server VMs to see if a number of VMs were booted at the same time. If so, then this is likely the cause.
Confio IgniteVM
Confio IgniteVM helps identify the impact of VM memory swapping for sites running Oracle on VMware, SQL Server on VMware, and other virtual databases. IgniteVM helps DBAs maintain performance and availability on virtual servers. IgniteVM is the only virtualization-aware database monitoring solution.
Learn more about IgniteVM solutions for:
- Eliminates need to set up contacts for each alarm
- Easy to see how all alarms are configured
- Lets VM administrators manage who is notified and under what conditions
