Page tree
Skip to end of metadata
Go to start of metadata

Last updated: May 21, 2020 10:16

This section includes content that no longer refers to the latest product version but may still be relevant if you are working with an older version.

The purpose of this article is to summarize Perfecto’s cloud lab requirements and best practices for the legacy Flash UI. Perfecto cloud labs use streaming services to give users access to devices from anywhere in the world (similar to Remote Desktop). Streaming services are more sensitive to latency and bandwidth limitations than other types of Internet use, such as web browsing. When you interact with a device in your cloud lab, a short delay of 1 to 1.5 seconds is expected. To prevent greater latency, planning is required.

This article covers the legacy Flash UI for Perfecto users, located at <YourCloud>

In this section:


TCP ports

This article covers how the mobile lab works, and the requirements for the Flash UI.

How the Perfecto Lab Works - Ports and Protocols


For one device, it requires 1.5 megabits per second of bandwidth, per user. For example, if three users connect to the cloud and each opens a single device, the necessary bandwidth would be three devices times the minimum bandwidth.


1 user and 1 device = 1.5 megabits per second of bandwidth usage 

3 users and 1 device each (3 devices total) = 4.5 megabits per second of bandwidth of usage (3x 1.5 megabits = 4.5 megabits)

If a single user opens more than one device, it takes an additional 256 kilobits of bandwidth per additional device, in the same session.


1 user and 1 device =

  • 1.5 megabits per second of bandwidth usage

1 user and 3 devices in the same session =

  • 1.5 megabits of bandwidth for the first device (1x 1.5 megabits = 1.5 megabits)
  • 0.5 megabits of bandwidth for the second and third device (2x 256 kilobits = 512 kilobits OR 0.5 megabits)
  • 1 megabits plus 0.5 megabits = 2 megabits per second total usage

2 users and 2 devices (two separate sessions) =

  • 3 megabits per second of bandwidth usage (2 x 1.5 megabits = 3 megabits)

2 users and 6 devices (two sessions, 3 devices each session) = 4 megabits per second of bandwidth usage

  • 1.5 megabits of bandwidth for the first device of each session (2 x 1.5 megabits = 3 megabits)
  • 0.5 megabits of bandwidth for the additional 4 devices in the sessions (4 x 256 kilobits = 1 megabit)
  • 3 megabits plus 1 megabits = 4 megabits per second total usage 

Important bandwidth considerations

While your site may have enough bandwidth, if many users share the same Internet connection as those who need cloud access, this can greatly affect the latency of the video stream. Bandwidth spikes from activities such as large downloads may cause intermittent problems. Many companies throttle bandwidth especially for RTMP video traffic to discourage employees from impacting available bandwidth as well as viewing sites with video such as YouTube, news, and other content that may not be work-related. Your IT department may not know that you need video streaming to use Perfecto clouds. This can cause your cloud to be treated as unwanted video streaming.

Whitelisting (allowing connectivity)

This is a process done by your Infra/Security teams to allow the Perfecto Lab services, to work with your company security. This involves rules and policies put in place to allow connectivity. Perfecto uses the following streaming services that deliver the content of a mobile device or desktop VM, from the cloud lab, to your workstation. These streaming services need to be allowed.

Streaming Servers (STS) list

Click on this hyperlink to see the flash streaming server list.

Reasons for slowness, latency, or delays

Streaming services can be slowed down by network appliances and rules/policies. This causes unpleasant delays, sometimes upward of 10 seconds or more, for manual testing.

Problems and Solutions

This section describes common problems and solutions.

Problem 1 | Devices are slow with high response times during manual testing

This happens when the streaming servers are being blocked, redirected, or are under traffic interception/scanning. The root causes can be blocked ports, SSL interception, deep packet scanning and IDS/IPS.

If you have already opened a Support Ticket, please utilize the Perfecto Network Connectivity Test. Then download the results and send them to us via the email chain started when you opened the Support Ticket.

If you see a delay between a manual click (such as on a number button in the calculator) during manual testing, and a response of...

  • Less than 2 seconds, you are getting good performance. Remember, this device may be thousands of miles away. Do not expect performance to be the same as though it's sitting in your hand. Nothing in this article will help you improve interactive latency below 2 seconds.
  • 2 to 3 seconds - Fair performance. You will notice that it is a remote device but you are able to get your work done. It may be possible to improve the performance slightly by applying best practices found in this article.
  • 3 to 4 seconds - Less than optimal. Waiting to see responses is beginning to impact your productivity. Definitely have your IT team look at this article.
  • Greater than 4 seconds - Unacceptable performance. Your network configuration is having a significant impact on your use of the Perfecto platform. Your IT team must provide a solution.

Solution #1: Allow connectivity to the Streaming Services

The best approach is to whitelist the Perfecto domain. This can be done by your Infra and Security teams by allowing * . This allows for minimal changes on the customer side, as we improve or add capacity to our services.

Note: On the flash UI, it is possible to whitelist both the URL and IP address, if necessary. Please see the link above in regards to the legacy flash STS.

Solution #2: Allow STS traffic without extra scanning

This solution ties in with Solution #1. Add a rule to allow the * traffic, to bypass SSL interception, deep packet inspection and IDS/IPS. Removing these additional security layers will help to improve overall manual cloud testing

Problem 2 | Automated testing appears to be slow

This tends to happen when a user first opens a device in session sharing, then runs a test against the device while it is open in the lab viewing

Solution #1:  Run automation without a lab device open in the lab view

To run true automation, first, do not open a device in the lab and do not share the session. Tests should run without any use of session sharing, or the device lab being open. Check your open device configuration capabilities and adjust as needed.

Solution #2: Check scripts for commands that loop or are unnecessary

We see that in many tests, there are looping commands. For instance, having a find element command loop several times over and over, when it is successful each time, can add delays to your tests. Performing debugging for script optimization

Strategies and practices to improve connectivity

Here are some suggestions on how to improve your connectivity to the cloud lab.

  • Isolate project teams in each location to their own VLANs. This allows bandwidth to be more easily controlled and measured.
  • Have your IT team assign a higher Quality of Service (QoS) priority to traffic from the cloud lab services, to your project team's VLANs.
  • Ensure that your IT department is not throttling bandwidth for the project team.
  • Consider a separate Internet connection for the project teams that will not be impacted by other users. Some customers use dedicated gateways for their testing team on an isolated network as a workaround.

Additional support

If you need additional support, contact the Perfecto Support Team. The Perfecto support team will be glad to assist with any questions or concerns that you may have in regards to delays, latency, etc.