For 10 months in the cold north, we are addicted to winter weather forecasts (ok, 10 months is a little extreme. Winter does not usually last that long in Minnesota). But during winter, we always want to know how much snow we are going to get. The answer always comes down to ranges
- Less than 1 inch
- 1-2 inches
- 2-4 inches
- 3-5 inches
- 5-8 inches
- 6-10 inches
- 8-15 inches
- Head south
As the totals get larger, the ranges get larger. There is so much room for error due to many variables.
The same thing can be said for estimating network bandwidth requirements for XenApp and XenDesktop. In another blog, I focused on Windows 10 bandwidth for XenDesktop. I want to now look at the same series of tests but for Windows 2016.
I broke the bandwidth estimate down into 3 categories
- VDA Version: Certain releases of XenApp make improvements to the network utilization. Bandwidth tests must account for these changes by looking at different VDA versions.
- Policy: XenApp policies can have a drastic impact on overall bandwidth utilization. With heavier compression (at the expense of CPU), overall bandwidth usage drops. Each test includes a look at WAN and User Experience policies (defined at the end).
- Workload: A user watching videos and browsing Internet content will consume significantly more bandwidth that someone mostly using Office applications. The workloads are broken down across task worker, knowledge worker and power worker.
First, let’s look at the averages for a 60 minute simulation:
By looking at averages, I can make out a noticeable bandwidth reduction for the task worker on a WAN policy between 7.11 and 7.15 releases. To get a better idea on the network bursts, let’s look at the 95th percentile
Again, we see a drop in the task worker with the WAN Policy between 7.11 and 7.15 release. I can also see a trend of dropping bandwidth in the Task worker with the user experience policy and WAN policy.
Let’s now look at application-specific usage:
The bandwidth usage for PowerPoint was surprisingly high. After looking into this, it turns out that there are really 2 numbers for PowerPoint. Presenting and creating. When creating, the bandwidth usage is similar to Word, but when presenting, the bandwidth spikes each time a slide changes.
What about bandwidth usage for video quality?
As expected, as the video quality increase, bandwidth usage also increases. I do find it interesting that with the WAN policy in 7.14, there was a noticeable increase in bandwidth across all video resolutions.Plus, for the user experience policy, there is a noticeable drop in bandwidth usage starting with the 1903 release.
And remember, these tests are simulations. Your results will be different because you are using real users with real workloads with real network congestion.
Note: The naming convention is follows: “Workload – XenApp Policy”
The XenApp policies are
|Dynamic windows preview||Prohibited||Enabled|
|Extra color compression||Disabled||Disabled|
|Limit video quality||Max 480p/720kbps||Not configured|
|Preferred color depth for simple graphics||16 bits per pixel||24 bits per pixel|
|Target frame rate||16 fps||30 fps|
|Target minimum frame rate||8 fps||10 fps|
|Use video codec for compression||Do not use video codec||For the entire screen|
|View window contents while dragging||Allowed||Allowed|