This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
Footprints in VMWare environmets All versions of 11.X and 12.X - 20.XX
How to diagnose performances in VMWare installed Footprints Servers ?
We have been asked for quite some time about the expected performances of a virtualized server on various types of virtualized environments.
Here are some tools to help improve performances on the application Server side, but also on the SQL Server one.
We do not have any specific documentation about virtualized environments, however it is possible to improve the performances in several ways.
This article specifically deals with virtualized environments using VMWare.
- 1 - Diagnose the Virtual Machine itself :
VMWare offers a specific tool which is dedicated to prepare the OS itself.
This is publicly available on this link : https://flings.vmware.com/vmware-os-optimization-tool
- 2 - Use optimization for the MSSQL hosted server:
Most interesting is the networking section and the importance to choose the appropriate virtual hardware, in order to benefit from the best capabilities of the device.
Here is the link to the pdf file : https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/sql_server_virtual_bp.pdf
- 3 - Be able to correctly set the memory in MSSQL Server :
Particularly helpful to use this in relationship with the VMWare pdf at section 2
- 4 - CPU Technical specifications :
A socket represents the chip implacement itself.
Cores are components of the inner chip.
Our documentation mentions a certain amount of CPUs depending on the simultaneous agents who are using Footprints.
These represent SOCKETS, and we ask the sockets to be multi cores, at least 2 cores.
So when you read 8 CPUs for 100+ users in our requirements, you must translate that into :
8 Sockets X 2 cores each (more if possible) = 16 virtual cores in total.
When the application server is also the SQL one, then the requiredspecifications for each individual servers ADD UP !
- 5 - Change the Virtual Machine's SCSI Controller type:
IT is preferable to create or activate the VMware Paravirtual controller type.
Have a look at this resource To configure an existing Windows boot disk to use a PVSCSI controller: https://kb.vmware.com/s/article/1010398
This page allows to better understand which controller type best suits the usage :
Let’ summarize this in a chart:
We are interested in the 1st line for Footprints usage and its associated database server.