Performance

Server preferences, screen update rates and how we measure them.

A screen with no viewer in range is kept, but not updated or sent. Nearby viewers get only the changed parts of the picture; viewers farther away get updates less often.

Server preferences in System

Sign in as an operator and open System on Home's operator page. Its SERVER section changes these values for the whole server; the choice chips show the active setting.

Viewer range: 32 blocks recommended. Larger ranges keep more screens active. A change applies from the next viewer scan.

Screen spacing: 16 blocks recommended. This is the minimum distance for new non-operator builds. Existing computers stay where they are; operators are exempt.

Update drop-off: 4 blocks recommended per halving of the send rate. Larger steps keep distant viewers more responsive, using more network traffic. A change applies from the next send, without changing app logic speed.

System also controls telemetry and, under APPS, which apps players may open. Disabling an app hides its tile and prevents opening or restoring it; an already running copy is not evicted and saved data is not deleted. Machine ownership and public/private kiosks remain in Settings.

Built-in lifecycle limits

These safety budgets are not System preferences.

LimitValue
Screen builds2 a tick
Liveness checks64 a tick
Teardowns8 a tick

Update rate at the recommended settings

Distance (blocks)Send rate (Hz)Interval
0-42050 ms
4-810100 ms
8-125200 ms
12-162.5400 ms
16-201.25800 ms
20-240.621.6 s
24-280.313.2 s
28-320.166.4 s

Network traffic

Only the parts of a screen that changed are sent, compressed, and a map whose contents a viewer already holds is skipped entirely. A first full paint is 16 KB for each map.

Per-app time budgets

A headless bench runs every app without Minecraft and checks it against 50 µs idle, 0.5 ms typical play and 4 ms for a full naive repaint, each tick (a tick is 1/20 of a second). These are our test limits, not server settings.