In this blog series, I take a look at scalability considerations for XenApp 6.5 Hosted Shared Desktops in especially:
- estimating XenApp 6.5 Hosted shared desktop scalability
- What is the optimum specification XenApp 6.5 VM?
- XenApp 6.5 for example Hosted shared desktop design
My last post has provided advice on the specification of the optimal virtual machine XenApp. Now, in the last post in the series, I'll walk through an example of sizing exercise.
Scenario
ABC Company has recently completed a user segmentation exercise. The following table includes 8 user groups that have been identified as good candidates for a hosted shared desktop. None of these user groups requires the ability to install applications and the ability to customize their desktop beyond changes depending on the profile. Provisioning Services three separate images will be created due to application compatibility conflicts identified by Citrix AppDNA.
With hosted shared desktops, it is important to consider the "Maximum number of simultaneous users" column rather than the "Total number of users column. Design environment for competition rather than the total number of users will help reduce infrastructure costs without compromising performance or availability.
sufficient redundancy must be built in the estimation of calibration so that a single host server or virtualization XenApp failure does not affect the total number of concurrent users that can be supported ( n + 1)
ABC company wants to use their standard hardware specification -. 2 sockets x 8 physical cores (16 physical cores / 32 virtual cores) with 128GB memory. Citrix XenServer will be used.
Number of XenApp virtual machines
According to the scenario described above, we have the size of the shared desktop environment Hosted so that it can support 750 light users and 1,100 regular users. Provisioning Services from multiple images are required, we will need to calculate the number of virtual machines required for each
First, we need to identify two values from the second blog post in this series :.
- Value to convert light users in normal (0.5)
- The number of regular users that can be hosted on a single XenApp server virtual machine during the use a virtualization host 2 socket (24)
image 1 (700 light users and 50 normal users)
Step 1: Convert all users to a normal workload
- 700 light users * 0.667 (blog 2) = 467 regular users
- 467 normal users +50 postion = 517 normal users
Step 2: Determine the number of XenApp virtual machines
- 517 regular users / 24 = 22 virtual machines XenApp
- 22 XenApp servers + 1 high availability server (+ 1 n) = 23 XenApp servers
image 2 (50 light and 750 normal users users)
Step 1: Convert all users to a normal workload
- 50 light users * 0.5 = 25 normal users
- 750 normal users + 25 = normal users 775 regular users
Step 2: Determine the number of XenApp virtual machines
- 775 regular users / 24 = 33 VMs XenApp
- 33 XenApp servers + 1 high availability server (n + 1) = 34 XenApp servers
image 3 (300 users normal)
Step 1: Convert all users to a normal workload
- not necessary that all users are already normal
Step 2: Determine the number of virtual machines XenApp
- 300 regular users / 24 = 13 virtual XenApp machinery
- 13 XenApp servers + 1 server for high availability (n + 1 ) = 14 XenApp servers
therefore, a total of 23 + 34 = 14 71 XenApp virtual machines will be needed .
The number of virtualization hosts
Referring to the second blog in this series, he tells us that each server with 32 virtual base 128GB RAM can support 8 x servers 4 vCPUs XenApp VMs
32 virtual cores / 4 virtual cores per virtual machine XenApp = 8 XenApp servers host virtualization
therefore, we will need a total of 9 XenServer hosts to support 66 virtual machines XenApp server:
66 XenApp VMs / 8 VMs per XenServer host = 9 guests virtualization
as n + 1 high availability is necessary, we must increase the number of XenServer virtualization hosts required to 10 . The XenApp load balancing functionality will be used to distribute the users between XenApp virtual servers in each workgroup.
Memory required
Referring again to the second blog post in the series, he tells us that every XenApp server on a host virtualization 2 socket usually requires 12GB memory. Therefore, 8 virtual XenApp servers x 12GB = 96GB. We also need to book an extra 752MB for XenServer. Because we have 31GB of physical memory remains, we will increase the memory allocated to each XenApp server with 3.5GB to 15.5GB -. If it is necessary
Disc Operations input / output per second
Referring to the second blog in this series, he tells us that each user requires 2 light stable IOPS and every normal user requires 4 IOPS steady state.
Local Storage
It is difficult to estimate IOPS XenApp server for local storage when using mixed workloads because we do not know how different types of workload will be distributed through virtualization hosts available. Therefore, we should estimate the worst case, which in this case is a normal user:
24 normal users per virtual machine XenApp x 4 IOPS = 96 IOPS stable condition by VM
8 XenApp server VMs per host virtualization x 96 steady state IOPS = 768 IOPS steady by the host virtualization
to achieve this number of IOPS local storage (disks spinning), we will need several disks in a RAID 10 configuration and a battery backup write cache. With the help of 1GB, more cache, we will probably need at least 4 local disks, 6 to be sure.
Shared Storage
The shared storage solution will need to be able to support a total of
750 light users x 2 IOPS = 1500 IOPS stable condition
1,100 regular users x 4 = 4,400 IOPS IOPS equilibrium
1500 + 4400 = 500 IOPS stable condition
and it ' is the last step in this sample period. I hope this has helped explain how to size the hardware requirements for shared hosted desktops
For more information on recommended best practices for virtualization Citrix XenApp, please refer to CTX129761 - .. Virtualization best practices
Andy Baker - Architect
Worldwide Consulting
Desktop Team & Applications
Virtual Desktop Manual
Accelerator Project
Follow @CTXConsulting
0 Komentar