How we test streaming in-house, with the numbers as they came out

The first test of streaming a RooF desktop from a GPU to a browser: what worked, what does not work yet, and why.

The RooF team

Why we build streaming ourselves

Today RooF sends the desktop to your browser over VNC, which is great for work and study. For games and video we need GPU-encoded streaming over WebRTC. Before promising anything on this site, we measured.

Step one: the GPU alone

On an NVIDIA RTX A6000 the GPU encoded 1080p60 at 520 frames per second, far faster than real time.1

Step two: 10 minutes over the internet

  • A mean of 59.95 fps at 1080p, with no dropped frames and no freezes.2
  • On a near network: 61 ms from click to picture (median).3
  • Over the internet: 251 ms (median), slower than we want for games.4

What did not pass yet, and why

The server we tested on only opens TCP connections, so the stream had to go through a TCP relay instead of UDP. On any network delay TCP waits for late packets, the jitter buffer grows and latency rises, and short audio gaps appeared. So we recorded the result as “partial”.

Bottom line: the GPU is ready; the network is what we are working on. We will not publish a gaming latency figure until this test passes from a server with UDP open.

What comes next

  • Run the same test from a server with UDP open, then from a region closer to the Gulf.
  • Publish the new numbers here and in the changelog as they come out.

Sources for these numbers

  1. STREAM-LEDGER: NVENC 1080p60 encode at 520 fps (8.7× real time)
  2. STREAM-LEDGER, 18 Oct 2026: 10-minute internet test, mean 59.95 fps, minimum 56
  3. STREAM-LEDGER: Chrome on a near network, click-to-photon 61 ms median, 77 ms p95
  4. STREAM-LEDGER: over the internet via a TCP relay, click-to-photon 251 ms median, 349 ms p95, with a 186 ms jitter buffer