VDI Sizing
“Workload type” column in Collector?
Collector has a column “Workload Type” in the VMInfo tab where you can define the workload type for each VM. Currently, only two type of workload is supported – Server Virtualization or VDI. The defualt is set to Server Virtualization as this workload has been supported since beginning.
For VDI, you can go to each VM and change the Workload Type to VDI against each row.
Note: User has to explicitly go to each row and set the Workload Type as “VDI” .We will change it to dropdown to make it more intutive in future.
Defining the workload profiles
Each VM which is marked as VDI is bucketed into one of the 25 profiles based on the CPU(MHz) and RAM allocated to the VM.
CPU
- Small <= (0-2000MHz)
- Medium <= (2000-4000MHz)
- Large <= (4000-8000MHz)
- X-Large <= (8000 – 16000 MHz)
- XX-Large <= (16000 – 32000 MHz)
RAM
- Small = <1.024GB
- Medium <2.048 GB
- Large <8.2 GB
- X-Large <16GB
- XX-Large <32 GB
The 25 workload profiles based on the above.
- VDI Small CPU Small RAM
- VDISmall CPU Medium RAM
- VDI Small CPU Large RAM
- VDI Small CPU X-Large RAM
- VDI Small CPU XX-Large RAM
- VDI Medium CPU Small RAM
- VDI Medium CPU Medium RAM
- VDI Medium CPU Large RAM
- VDI Medium CPU X-Large RAM
- VDI Medium CPU XX-Large RAM
- VDI Large CPU Small RAM
- VDI Large CPU Medium RAM
- VDI Large CPU Large RAM
- VDI Large CPU X-Large RAM
- VDI Large CPU XX-Large RAM
- VDI X-Large CPU Small RAM
- VDI X-Large CPU Medium RAM
- VDI X-Large CPU Large RAM
- VDI X-Large CPU X-Large RAM
- VDI X-Large CPU XX-Large RAM
- VDI XX-Large CPU Small RAM
- VDI XX-Large CPU Medium RAM
- VDI XX-Large CPU Large RAM
- VDI XX-Large CPU X-Large RAM
- VDI XX-Large CPU XX-Large RAM
Storage for each workload profile is calculated by adding the capacity for each VM in that profile (same as done for Server Virtualization)
Sizer asks for the VDI attributes upon Collector import:
Defualt values already selected.
The default values ( or user selected values ) captured here becomes the basis for initial VDI sizing.
Edit workload :
User can go to each VDI workload and make edits. However, this will overwrite the data collected from Collector (for ex: on capacity,ram etc) . The standard pre-defined templates ( defined in the normal VDI sizing) is applied once edited and parameters changed( like worker type, provision type, etc).
VM Performance data:
Collector also has performance data for the VMs collected over a 7 day period. The VM CPU utilization over past 7 days collected at 30 minute interval is collected and displayed. in the UI. While sizing, users can either go with allocated CPU or factor in the utilization rate to optimise on the overall CPU requirement for the VMs based on their historical usage. Basically, the utilization rate is a multiplier to the allocated CPU and a buffer is added to come up with net CPU. For more information on that, please refer to the Collector section.