Findings Video conference with Azure Virtual Desktop using Teams

December 31, 2021
Thomas Poppelgaard
AMD, Azure, Microsoft, Teams

Introduction

Over the last couple of years, there has been an impressive flux with many businesses and institutions adopting and relying on large-scale remote working and remote learning environments to maintain workforce and learning continuity. During this time, it’s generally been recognised that this type of remote working/learning has been quite successful, with many businesses and institutions continuing remoting working/learning practices or introducing hybrid models with a combination of remote and office work for their staff.

One of the reasons why remote working/learning has been successful is the availability of supporting technologies that have delivered a high standard of human communication and engagement across large numbers of workers or students/faculty in remote environments. Video conferencing applications, which includes video conferencing, screen sharing, IMs and more, are such technologies that have contributed to viable remote working/learning environment success.

But to use these applications to their fullest potential, a robust IT infrastructure is also a must. Many large enterprise companies, as well as SMB and other institutions have centralised their IT environment into virtualized desktop infrastructure (VDI), either as an on-premises solution or as a managed-service by cloud service providers (CSP). Centralizing resources, applications and data into a single infrastructure allows for better IT management and security of vital resources and data which can help improve workforce productivity, data security and IT efficiencies.

Investigation overview

This blog details a recent technical investigation where popular video conferencing applications are deployed on AMD-based Azure instances to determine the performance of each application, the number of deployable users in a multi-session environment, and the user experience each person would receive. The AMD-based instances includes both CPU-only based instances and CPU+GPU based instances to understand the impact of GPU-enabled resources to the density and experience of the users.

So next let’s look at the various parameters for the investigation.

The Lab:

For the investigation, we had three areas of consideration:

Azure Session Host

For the host, we used Microsoft Azure. The system used Windows 10 Multisession 1909, running on Microsoft Remote Desktop Protocol (RDP) in Azure Virtual Desktop. The instances used are NV32asV4 (32 vCPU/112 GB/ 1xGPU), D32av4 (32 vCPU/112 GB) and D32sv4 (32 vCPU/112 GB). The host was in West Europe (Amsterdam) and the tests we conducted in Hinnerup, Denmark – with a rough distance of 500 miles from the datacenter.

Applications

The applications we used as part of this investigation are listed below. These are the most used video conferencing applications used to for remote working/learning.

1) Microsoft TEAMs

Teams WebSocket Service is installed and teams is installed per-machine mode according to microsoft docs to get Teams optimization for AVD supported in a best configuration so it offloads to the endpoints that supports this.

Endpoint devices

The investigation looked at using physical end point devices as opposed to virtual, giving a truer representation of the environment and experience. This as a result limited the sample size to 15+1 concurrent users, due to lab space.

Within the sample size, we used 11x Windows PCs, 5x Chromebooks and 1x MacBook Air laptop. Each device used the latest OS. In relation to the workload, we have 15 users connected and 1 additional user as host of the video call.

The workload:

For the investigation we looked at three types of workloads typically seen with video conferencing and run over a 30-minute period:

Workload 1 (length of time: 30mins)

1x host and 14x guest video conference (video and audio sharing) +Screen sharing static (PDF) content

Workload 2 (length of time: 30mins)

1x host and 14x guest video conference (video and audio sharing) +Screen sharing dynamic (video) content

Workload 3 (length of time: 30mins)

1x host and 14x guest video conference (video and audio sharing) +Screen sharing dynamic (video) content+Guests are multi-tasking, taking notes on office 365 suite

These workloads will become more demanding because of the increase in workload requirements – with video and audio sharing to dynamic screen-sharing to to multi-tasking. This gives a set of different types of common uses cases seen in remote working/learning environments.

Methodology

There are two areas in which we are collecting the data for this investigation.

How are we collecting the data?

This image has an empty alt attribute; its file name is image-5.png

The data was captured each 3 seconds using the Windows OS system from Sepago’s Azure Monitor for AVD monitoring tools. This allowed for cross checking of the data delivered

Considerations

Not all applications and devices are built the same

Before we look at the results of this investigation, we also need to reflect on the parameters and support each of the applications has for the different end-point devices as well as how they are viewed/installed.

Microsoft TEAMS

For this application, we can see in the below table there is general support across the typical platforms, however some have more features and support compared to others.

Importantly, “Windows desktop” is the only platform that supports TEAMS media optimization – Which pushes the audio and video processing locally to the Windows Desktop client for Teams calls and meetings freeing up more host resources for greater numbers of users on the VM. This is done not be installing a dedicated client but it being built into and optimised for Windows Desktop Client.

For the other devices connected to the host, in this case the 5x Chromebooks and 1x MacBook devices as they are not supported by the TEAMS media optimisation it means the audio and visual processing is done on the host – taking more host resources as a result.
* Microsoft have released preview client (macOS Remote Desktop client, version 10.7.7 or later (preview)) feb 2022, which now supports Teams redirection, beta client can be downloaded here:
Part of this investigation the beta client was not used

Azure Virtual Desktop redirection support

Another area to consider is Azure Virtual Desktop support for audio and camera redirection with end-point devices. Redirection helps to improve latency with camera and audio as its essentially a pass-through to the host.

Camera – redirection camera support for AVD is supported with Windows devices and MacOS – this means no redirect support for ChromeOS and HMTL5 (Web client). So there is an expectation to see more latency with ChromeBooks and devices connected via a Web client.

Speakers – with AVD, speaker redirect support is across all platforms, whether is Windows, ChromeOS, MacOS and HTML5.

Investigation findings

In the section we are going to review the findings from the investigation. Just to reiterate, there was 3x session hosts with 1x applications tested against 3x workloads, giving a total of 9 findings. Let’s begin….

Microsoft Azure NV32as_v4

Metrics captured each 3seconds with 15 concurrent users using AVD

Observations:

ALL 3 workloads works great across devices, video in sync and audio.
Delivered a great user experience

Microsoft Azure D32as_v4

Metrics captured each 3seconds with 15 concurrent users using AVD

Observations:

ALL 3 workloads works great across devices, video in sync and audio.
Delivered a great user experience

Microsoft Azure D32s_v4

Metrics captured each 3seconds with 15 concurrent users using AVD

Observations:

ALL 3 workloads works great across devices, video in sync and audio.
Delivered a great user experience

Summary, scalability, user experience and recommendations

I will cover in my findings what does the data means when it comes to scalability and user experience.

Scalability

Lets look at some raw data. Instance was benchmarked with 15 CCU and if you divide CPU util with 100% and multiply with 15x this is how I did the raw estimate.

Please keep in mind this is a raw estimate so keep the data with caution