Features · Performance
Fast to type into. Fast to come back to.
The host sends your screen only what changed. A key press echoes in 1.19 ms, and 64 terminals are back on screen 19.8 ms after a reconnect.
Typing
- Key press to echo, p50
- 1.19ms
- 1,000 terminals running, same machine. p99: 1.28 ms.
- Key press to echo in a browser, p50
- 1.18ms
- Through the host's gateway over WebSocket. WebTransport: 1.16 ms.
- Host CPU per key press
- 15µs
- 1,000 terminals typed into at 4 keys per second each.
Reconnecting
- 64 terminals back on screen
- 19.8ms
- Each with 10,000 rows of output, same machine.
- 64 terminals' screens over a network
- 173ms
- 100 Mbit/s, 20 ms round trip. At 80 ms: 622 ms.
- 16 terminals' screens in a browser
- 9.5ms
- Through the host's gateway over WebSocket. WebTransport: 2.4 ms.
Scale
- Host memory per terminal
- 282KB
- 1,000 idle shells on one host: 290 MB in all.
- Of one CPU core for 1,000 idle terminals
- 6.2%
- 12.2% while all 1,000 are typed into.
- Per frame from a busy terminal
- 835B
- 100 new lines a frame, 4,977 rows of history kept.
What it does.
- How we measure
- Medians of 5 runs of Ubik's benchmarks, each in a fresh process, on a Linux workstation pinned to 8 cores. Your hardware, network and programs change the numbers.
Start on this machine.
The desktop app comes with a local host. Add a remote one when you need it.