In this blog series, I'll take a look at some of the scalability considerations for XenApp 6.5, including:
- estimate XenApp 6.5 Hosted shared desktop scalability
- What is the optimum specification XenApp 6.5 VM?
- XenApp 6.5 dimensioning example Hosted shared desktop
then First, let's look at how you can estimate XenApp 6.5 shared desktop scalability.
In an ideal world, each project would include time for testing scalability so that the right number of specified optimally servers can be ordered. However, there are several reasons why this does not happen always, including the time and budget constraints. And often, architects are invited to give their best estimate of the resources needed to support a VDI environment.
I'm in that situation myself and I know how stressful it can be. Do you specify that you will cost your company money. If you specify as you will reduce the number of users that can be supported - or even worse, you will have a performance impact
To help improve estimates of equipment, I tried to XenApp 6.5 scalability advice by. the screening test results from a variety of sources, including customers, suppliers and internal testing teams. I documented test results in a spreadsheet so I can look for patterns between the user density, the workload and the specification of the server.
The first thing I notice is that the processor subsystem is always the primary bottleneck for XenApp 6.5. It is not surprising that XenApp 6.5 is 64-bit only, as long as you do not spoil the RAM allocation that you will not run out of memory.
I saw a lot of variation between trials due to the number of processors, physical cores, processor speed, the user workload, the use of antivirus management tools and if the XenApp servers hosted published applications or desktops. However, once I adjusted the results based on these factors, I could see a pattern emerging between the number of available physical cores and user workload:
Interestingly, the test results have shown that the transition from two to quad processor servers is not linear and this was reflected by a 15% decrease of the user density by heart - not caught by this
the next step was to use this formula to estimate the density of users for some of the most common processor specifications there:
why these lower estimates to normal? The reason is that I made allowances for factors which are not always included in the process of scalability tests - such as antivirus implementation, management and monitoring software tools. All who have a significant impact on the scalability
One thing to keep in mind is that these estimates are based on the following conditions :.
- The processor speed has a direct impact on the number of users that can be supported per processor. The estimates provided are based on processor speed of 2.7 GHz.
- Hyperthreading is enabled on the virtualization host.
- The light, normal and heavy workloads are not mixed within a XenApp server or virtual host of physical virtualization.
- Flash redirection is enabled.
- assumes that all workloads include antivirus and monitoring tools / management standard.
- The recommended XenApp optimizations have been implemented. For more information, please refer to the knowledge article Citrix CTX131577 -. XenApp 6.x Optimization Guide
- There are many definitions of what constitutes a light, normal and heavy users. I followed the previous guidance of Citrix
- Light One or two applications no activity browser-based
- Normal :. multiple applications with browser-based activity
- heavy :. Few applications, but needs heavy system resources. Data processing, compilation of handling, or graphics are common applications
For the recommended best practices for virtualization Citrix XenApp, please refer to CTX129761 - .. virtualization best practices
Andy Baker - Architect
Worldwide Consulting
desktop Team & Applications
Virtual Office Handbook
Accelerator Project
Follow @CTXConsulting
0 Komentar