In general, there are three key parameters that affect the performance of your streaming experience on Frame, each of which you can monitor in real time when running a session:

  1. Network bandwidth - the volume of data per unit of time that an internet connection can handle.  For Frame, your "downstream" bandwidth is most important, especially if you are working with apps that have a lot of graphical motion and changes and/or you are using a large monitor with a high resolution (which results in more data needing to be streamed).  

    Upstream bandwidth, however, also affects performance - and while it does not need to be as much as your downstream bandwidth, being as close to a "balanced" connection as possible is best.  

    In general, we recommend a downstream bandwidth of at least 3 Mbps and at least 1 Mbps up.

    In your session, color-coded dots at the bottom of the screen represent network bandwidth:

    User-added image

    If your connection's bandwidth is adequate, you should see four or five green dots. If the bandwidth is less than desirable, the dots will reflect this with fewer dots and turn orange, and ultimately red (one dot, which is a very poor connection). The dots translate to Mbps per below:
    1  dot:  less than 1Mbps
    2 dots:  1 - 2 Mbps
    3 dots:  2 - 4 Mbps
    4 dots:  4 - 8 Mbps
    5 dots:  more than 8 Mbps
  2. Network latency - how much time it takes for a packet of data to get from one point to another, round-trip.  In our case this affects the responsiveness of your session to your inputs.  For example, when you click your mouse - that information is sent to our remote servers, the movement is interpreted, and the change in the screen is sent back to you.  

    Naturally, a key thing that impacts latency is the distance between the server and your session.  In general, a latency of under 100 ms for a Frame session will deliver a good experience. In your session, latency and distance are shown like this:

    User-added image

    Note that the distance calculation is based on where your local network's IP address was registered.  So this distance measure is only approximate for rough guidance  --  the latency measure is what matters the most.
  3. CPU - processing resources of the local machine, required for decoding video sent directly to the browser.  When running Frame sessions in a browser, the decoding of the video stream is generally done in the device's CPU.  If your local machine doesn't have enough available CPU resources (e.g. you are simultaneously running some other active apps like video conferencing or games) - then this can affect the performance of your session.  

    Checking CPU usage is specific to your device.  For example, use Task Manager (Windows, Chrome), or Activity Monitor (Mac OS X).