This guide will help on preparing the Session Host in a vSpace Pro environment as well as vSpace 6 Environment. However, there have been several improvements on our new vSpace Pro platforms that will even make it more resource effective than its predecesor vSpace 6.
For example, let's look at our transport protocol UXP 2.0, as described on our vSpace Pro webpage
"If you are using vSpace 8 or 10, migrating to vSpace Pro Enterprise Edition will make a noticeable difference. As an example, the L300 will see up to a 27% reduction in traffic, while RX300 and vSpace Pro Client for Windows will see as much as a 43% traffic reduction"
If your particular use case involves in playing back Youtube web video (with Chrome browser) or local video playback (with VLC player), the built-in vCAST streaming technology would significantly decrease CPU resources and increase the margin for more user density. In this case, per the instructions below on choosing a processor, the maximum user calculation would be based on 'low workload' calculation instead of 'high workload'.
This is an amazing benefit of using vCAST Streaming Technology by offloading the server side processing, directly to the client side (via vCAST).
In virtue of the above, you may use this guide as an estimator for your resource allocation for vSpace Pro Platforms and the new RX300 Devices.
One of the principal advantages of deploying multiple users on a single host–be it a PC, physical server or virtual machine–is that you can readily scale the size of your deployment as your users’ needs grow. Rather than being forced to purchase expensive new computing resources for each new user, you can simply expand the capacity of your host system.
The number of users, intended application suite and overall performance expectation determine how powerful a host system must be in order to deliver the desired end-user experience. This document provides high-level guidelines for determining the system requirements for various numbers of L-series and M-series users with various computing workloads. This document can be used as a starting point for sizing your deployment – but your own in-house testing should be used for the final determination of your host systems’ configurations.
Prior to deploying vSpace, you should develop use cases for the users you expect to connect to a host. An important consideration in developing use cases involves determining the number and types of applications users will need to operate. These requirements help you identify and measure the users’ standard workloads. For example, you should measure the CPU, memory and storage utilization for a typical user workload in your environment. This workload data and the total expected number of users will help you determine the system requirements for your host system.
For the purpose of our testing, workloads were divided into three typical usage scenarios each of which involved sequentially cycling through and completing tasks within the listed applications. These workload profiles have been detailed below.
Choosing a Processor
The website http://www.cpubenchmark.net/
has informative data we can use as a measuring tool in order to estimate the right candidate for a processor. All processors are arranged in order of "PassMark CPU score", based on server orientated benchmark testing.
In order to come up with the right PassMark number, first, there has to be a calculation of the users’ standard workloads.
As an example, we have the following three typical usage scenarios. The details below are only suggestions of what each scenario looks like.
Low Workload Scenario
• Microsoft Office® applications: one instance of Word and Excel® per user
• Adobe® Reader 10 — opening and viewing a PDF file
• Internet Explorer®, with two windows/tabs active
Medium Workload Scenario
• Microsoft Office applications: one instance of Word, Excel and • PowerPoint® per user
• Adobe Reader 10 — opening and viewing a PDF file
• Internet Explorer, with three windows/tabs active
High Workload Scenario
• Microsoft Office applications: one instance of Word, Excel and PowerPoint per user
• Adobe Reader 10 — opening and viewing a PDF file
• Internet Explorer, with four windows/tabs active
• Video file (played in Windows Media Player) in a half-screen size window at 480p resolution
Now that there is an idea of what the workload looks like, see the base numbers below to get a base number for the final PassMark calculation:
Low workload: 300
Medium workload: 400
High Workload: 600 to 800
(Note: Base numbers for video streaming, higher than 480p in all sessions, will be greater than the above suggested numbers)
Now, taking the base number for any of the workload estimations above and multiplying it by the number of sessions that are planned to have, will total the PassMark number needed in order to estimate the CPU choice.
For example, let's say that you are looking to build a medium workload system, and you want it for 30 users. So the equation will be as follows:
300 X 30 = 9000.
The final number is your Passmark score and is the number that will help you estimate your CPU. As you can see in the PassMark website, an Intel Core i7-3820 @ 3.60GHz will correspond to this number and can be the desired candidate for this system.
RAM should be estimated as 0.5 to 1 Gb per user, depending on the estimated workload.
Selecting a Hard Disk
Choose a high RPM disk. 10,000 RPM or 15,000 at least. Solid State can give you best results.
Adding a video card that supports DirectX 11 or higher has shown to improve performance for some applications.
As a final comment, once again, we remind you that this document is provided to you as a starting point for sizing your deployment, but your own in-house testing should be conducted for the final determination of your host systems’ configurations.
We hope this information is helpful to you.