[List of Test Results Obtained in EUC Score Experiments]
Analyzing Desktop as a Service performance on Azure, Amazon Web Services (AWS) and Google Cloud Platform (GCP), with and without GPU. Remoting protocols are Frame Remoting Protocol (FRP) and Microsoft Remote Desktop Protocol (RDP). The test results presented here are a subset of the complete datasets collected during multiple DaaS test sequences.
It is important to note that with default settings the Frame Remoting Protocol (FRP) delivers 60 frames per second while Microsoft RDP delivers 30 frames per second to the endpoint device. This may result in higher network consumption on the FRP side.
If you want to learn how the EUC Score results were produced then check out EUC Score Test Methodology and EUC Score Toolset.
Testable question: How does a Frame Remoting Protocol (FRP) connection to a Windows desktop on Azure compare to an RDP connection to a physical Windows workstation?
RDP Connection to Lancelot
FRP Connection to Azure VM
System Under Test: Physical Lab Machine Lancelot, Windows 11, Intel i7-11700K 16Threads @ 3.6GHz, 64GB RAM, Crucial MX500 SSD 1TB, NVIDIA Quadro M5000, 8GB VRAM.
System Under Test: Azure West Europe, different VM types with NVIDIA and AMD GPUs, Frame Display Driver.
Connection: RDP-UDP from Remote Desktop Connection Client, 20ms round trip time.
Connection: FRP8 UDP from Chrome browser, 4ms latency.
Sync Player Clip | View and Type | Observation | |
---|---|---|---|
![]() |
SL1-MSEdgeAquariumWebGL | SxS View - GPU | Azure NC4asT4-v3 VM with NVIDIA T4 GPU: 650 FPS vs 800 FPS and smoother animation on the Azure side (40% CPU load). |
![]() |
SL1-TessMarkOpenGL | SxS View - GPU | Azure NC4asT8-v3 VM with NVIDIA T4 GPU: Smoother animation and better rendering quality on the Azure side. Less overall CPU load (20%) when compared to the NC4asT4 v3 VM with approx. 40% load. |
![]() |
SL1-FurMarkOpenGL | SxS View - GPU | Azure NV12adsA10-v5 VM with NVIDIA A10-8Q vGPU: Slightly better user experience on the Azure side, despite the partitioned GPU. |
![]() |
SL1-WMPlayer1080pMP4 | SxS View - GPU | Azure NV4as-v4 VM with 1/8 AMD Radeon MI25 GPU: Without a video decoder in the GPU, video playback falls apart. |
![]() |
SL3-FractalsPythagoras | SxS View - GPU | Azure NV4as-v4 VM with 1/8 AMD Radeon MI25 GPU: The CPU/GPU combo is not powerful enough for the fractals score. |
Result: On Azure NC4asT4-v3, NC4asT8-v3 and NV12adsA10-v5 VM types, the overall performance is better than on the physical lab machine Lancelot. But when the combination of CPU and GPU is less powerful, the physical lab machine Lancelot performs better.
Testable question: How does a Frame Remoting Protocol (FRP) connection to a Windows desktop on AWS Workspaces compare to an RDP connection to a physical Windows workstation?
RDP Connection to Lancelot
FRP Connection to AWS VM
System Under Test: Physical Lab Machine Lancelot, Windows 11, Intel i7-11700K 16Threads @ 3.6GHz, 64GB RAM, Crucial MX500 SSD 1TB, NVIDIA Quadro M5000, 8GB VRAM.
System Under Test: AWS eu-central-1, EC2 g4ad.xlarge with AMD Radeon Pro V520 MxGPU or EC2 g4dn.2xlarge VM with NVIDIA T4 GPU, Frame Display Driver.
Connection: RDP-UDP from Remote Desktop Connection Client, 20ms round trip time.
Connection: FRP8 UDP from Chrome browser, 4ms latency.
Sync Player Clip | View and Type | Observation | |
---|---|---|---|
![]() |
SL1-ChromeWaterWebGL | SxS View - GPU | AWS g4ad.xlarge VM with AMD Radeon Pro V520 MxGPU: The quality of the animation is much better on the AWS side. |
![]() |
SL1-ChromeCarVisualizer | SxS View - GPU | AWS g4dn.2xlarge VM with NVIDIA T4 GPU: Car rotates significantly faster on the AWS side. |
![]() |
SL1-FurMarkOpenGL | SxS View - GPU | AWS g4dn.2xlarge VM with NVIDIA T4 GPU: Very smooth rendering and animation of the fur donat on the AWS side. |
Result: The overall performance of the AWS DaaS VM types is better than on the physical lab machine Lancelot. The CPU on Lancelot shows less load due to higher CPU thread (= core) number and higher clock rate.
Testable question: How does a Frame Remoting Protocol (FRP) connection to a Windows desktop on Goggle Cloud Platform compare to an RDP connection to a physical Windows workstation?
RDP Connection to Lancelot
FRP Connection to GCP VM
System Under Test: Physical Lab Machine Lancelot, Windows 11, Intel i7-11700K 16Threads @ 3.6GHz, 64GB RAM, Crucial MX500 SSD 1TB, NVIDIA Quadro M5000, 8GB VRAM.
System Under Test: GCP europe-west4, N1-Standard-4-GPU-T4-Windows VM with NVIDIA T4 GPU, Frame Display Driver.
Connection: RDP-UDP from Remote Desktop Connection Client, 20ms round trip time.
Connection: FRP8 UDP from Chrome browser, 4ms latency.
Sync Player Clip | View and Type | Observation | |
---|---|---|---|
![]() |
SL1-MSEdgeAquariumWebGL | SxS View - GPU | GCP N1-Standard-4-GPU-T4-Windows VM with NVIDIA T4 GPU: Higher frame rate and smoother animation on the GCP side, despite the much less powerful CPU. |
Result: The performance of the GCP DaaS VM types is better than on the physical lab machine Lancelot. The CPU on Lancelot shows less load due to higher CPU thread (= core) number and higher clock rate.