Why is my WorkSpaces performance slow?

Short description

The following reasons can cause slow performance of a WorkSpace:

• Outdated WorkSpaces client version
• High round-trip time (RTT)
• High CPU usage
• VPN or proxy issues
• Configuration issues

Resolution

Reboot the affected WorkSpace

Use the WorkSpaces console to reboot the affected WorkSpace.

Verify your WorkSpaces client version

To verify that you're using the latest WorkSpaces client version, complete the following steps:

1. Identify your WorkSpaces client version:
   For Windows, choose the Settings icon, and then choose About Amazon WorkSpaces.
   For Linux, choose the menu icon, and then choose About.
   For macOS, in the navigation bar, choose WorkSpaces, and then choose About WorkSpaces.
2. Choose Download Latest Client. This opens the WorkSpaces client URL in a browser.
3. Select the WorkSpaces client for your operating system. Then, to check the latest available version, choose Release Notes.
4. If your WorkSpaces client is out of date, then navigate back to the Amazon WorkSpaces client download page.
5. Select the platform for your client machine.
6. To install the latest client, choose Download.

Verify your RTT and review CloudWatch metrics

To check the RTT between the client location and the WorkSpaces AWS Region in real time, choose the network icon. For more information, see Client network requirements for WorkSpaces Personal. You can also verify your RTT with Connection Health Check.

Use Amazon CloudWatch metrics to monitor the InSessionLatency and CPUUsage metrics.

For information about how to troubleshoot graphics-intensive applications, see I am getting a "network connection is slow" warning when connected to my WorkSpace.

Diagnose high CPU usage (Windows only)

Consistently high CPU usage causes low performance. For more information, see How do I diagnose high CPU utilization on my EC2 Windows instance when my CPU is not being throttled?

Validate VPN or proxy issues

Check if the performance issues occur only when you use a VPN or proxy to connect to WorkSpaces. A VPN might have bandwidth constraints that cause slow performance. Complete the following steps twice, once with your VPN on, and then once more with your VPN off:

1. To review your network stability, run the following command for the WorkSpaces API endpoint for your Region:

   ping -t workspaces.sa-east-1.amazonaws.com

   Note: Replace workspaces.sa-east-1.amazonaws.com with your Region.
2. Let the ping run for at least 30 minutes to capture enough data points to check if your network is stable. To end the ping, press Ctrl-C.
3. Check the output for the Minimum, Maximum, and Average values. If your network is stable, then these values are similar. If any pings fail, or if you have RTT outliers in your ping, then your network is unstable.
   Note: If all pings time out, then your network might be blocking Internet Control Message Protocol (ICMP) traffic.

To improve network stability, replace your computer's wireless Wi-Fi connection with a wired connection to the network.

If users must access their WorkSpaces through a VPN, then make sure that your network meets the minimum requirements for maximum transmission units (MTU).

Test your WorkSpaces connection

To test if you still experience latency, use Remote Desktop Protocol (RDP) to connect to your WorkSpace.

Check your antivirus software

If you installed an antivirus software on the WorkSpace, then make sure that it doesn't interfere with the service components. Exclude the required WorkSpaces service components.

Reconfigure your WorkSpace

If you use a PCoIP WorkSpace, then migrate your WorkSpace to WorkSpace Streaming Protocol (WSP). Use WSP when you need higher loss and latency tolerance to support end user network performance. For more information, see When to use WSP.

If you're using a low compute type, then increase your compute type to a higher bundle. Then, check your WorkSpaces performance.

Collect client and bundle logs

If you still experience performance issues after you complete the previous troubleshooting steps, then collect your client and bundle logs and open a support case. To learn more about advanced logging, see Activating advanced logging. To learn more about bundle collection, see Automated server-side log bundle collection for Windows.

Related information

Connection health check