Gathering information about users, applications, hardware, and the environment is important for properly sizing a VDI deployment. Key factors to consider include CPU, memory, storage, and network requirements. Parameters like the virtual CPU to physical CPU ratio, memory allocation per virtual machine, storage space per user, and profile type will determine how many virtual machines can be supported on each host. Requirements for Horizon, vCenter, ESXi, and other components must also be taken into account.
Gathering information about users, applications, hardware, and the environment is important for properly sizing a VDI deployment. Key factors to consider include CPU, memory, storage, and network requirements. Parameters like the virtual CPU to physical CPU ratio, memory allocation per virtual machine, storage space per user, and profile type will determine how many virtual machines can be supported on each host. Requirements for Horizon, vCenter, ESXi, and other components must also be taken into account.
Gathering information about users, applications, hardware, and the environment is important for properly sizing a VDI deployment. Key factors to consider include CPU, memory, storage, and network requirements. Parameters like the virtual CPU to physical CPU ratio, memory allocation per virtual machine, storage space per user, and profile type will determine how many virtual machines can be supported on each host. Requirements for Horizon, vCenter, ESXi, and other components must also be taken into account.
Gathering information about users, applications, hardware, and the environment is important for properly sizing a VDI deployment. Key factors to consider include CPU, memory, storage, and network requirements. Parameters like the virtual CPU to physical CPU ratio, memory allocation per virtual machine, storage space per user, and profile type will determine how many virtual machines can be supported on each host. Requirements for Horizon, vCenter, ESXi, and other components must also be taken into account.
1- Gather info: ================= - What application the user need? - Are the app. more cpu, or memory intensive? - Are there an excessive number of storage operation? - What type of N/W load generated by users? - What type of peripherals the users are connected to? - What’s the available network bandwidth? - What are the type of users? - How many locations are there? - What type of endpoints to be used? - What storage solution the customer is running? 2- Sizing the environment: ============================= VDI Requirements
4 Parameters for Sizing the Environment:
CPU Memory Storage Network
CPU A good, conservative starting point in the design is 6 vCPUs per pCPU when calculating density. This ratio of vCPU:pCPU is called the overcommit ratio. After you have determined the optimal vCPU:pCPU ratio in your design, your virtual-machine-per-host sizing can follow this simple formula: (Virtual Machines per Server) = ((Cores Available on Server) / (vCPUs needed per Virtual Machine)) * (Overcommit Ratio of vCPUs per pCPU)
RAM As a guideline, for balance between performance and memory utilization, the virtual machine should have Approximately 25 percent more RAM allocated than the maximum active load on the virtual machine. This allocation prevents Windows from writing data to its paging file and keeps the active working set (applications and data) for the virtual machine in RAM instead of in virtual memory space.
Windows 7 64-bit enterprise deployment requires 2 vCPUs and 4GB RAM.
(For a Windows 7 32-bit virtual machine guest with 2 vCPUs, a minimum of 2GB RAM is recommended.) The native OS alone is approximately 400MB. The goal is to allocate enough memory to hold the set of applications and data while keeping the memory overcommit ratio as low as possible. This prevents Windows from writing data to the paging file because there is not enough RAM available in the guest OS
Memory should not be oversubscribed in a VDI deployment. There should
be sufficient RAM in the host, plus 25 percent for vSphere and swap overhead, and potentially more if 3D is being used
Storage The Windows 7 64-bit version requires an additional 4GB of disk space over the Windows 7 32-bit version. This will decrease the number of virtual machines on your server, unless additional storage can be added
The maximum virtual machines per LUN is 128 for Fiber Channel, and an unlimited number of virtual machines for NFS and iSCSI place View Composer replicas on solid-state disk drives Profile: Most cases 500 MB profile per user There are three types of profiles available for use in a terminal services environment from Microsoft—local, roaming, and mandatory profiles. Which profile type an organization decides to go with will be dependent on the decision made about the overall environment? • Local profiles are used when the settings in the profile do not matter as a user roams from desktop to desktop. • Roaming profiles allow user settings to be persistent across logins and across machines, ensuring a consistent user experience no matter which desktop a user logs in to. • Mandatory profiles provide groups of users with a single profile, and changes to the profile are discarded upon logout. Virtual Desktop Configuration by User Type
• Task-based workers – Limited applications and limited performance
requirements • Knowledge workers – Standard office applications and medium performance requirements • Power users – Compute-intensive applications and high performance requirements Horizon, vCenter & ESXi Environment Requirements:
Horizon Connection Server Hardware Requirements
These requirements also apply to replica and security server Horizon
Connection Server instances that you install for high availability or external access
vCenter Server Hardware Requirements
VMware recommends having a one-to-one mapping between each View
Composer service and vCenter Server instance View Composer Hardware Requirements
ESXi Hardware Requirements:
ESXi 6.7 requires a host machine with at least two CPU cores
ESXi 6.7 requires a minimum of 4 GB of physical RAM. It is recommended to
provide at least 8 GB of RAM to run virtual machines in typical production environments
ESXi 6.7 requires a boot device that is a minimum of 1-GB. When booting from a local disk, SAN or iSCSI LUN, a 5.2-GB disk is required to allow for the creation of the VMFS volume and a 4-GB scratch partition on the boot device Horizon 7 Sizing Limits & Recommendation https://kb.vmware.com/s/article/2150348
Building Cloud and Virtualization Infrastructure: A Hands-on Approach to Virtualization and Implementation of a Private Cloud Using Real-time Use-cases
Building Cloud and Virtualization Infrastructure: A Hands-on Approach to Virtualization and Implementation of a Private Cloud Using Real-time Use-cases
