- The desktop measured: Horizon v2026.10.22.13 against vanilla 26.3 at render
distance 12 and 32, 3 runs each, 1280x720, VSync off, in a headless sway on
the RTX 4080 (never on its screen). Replaces the "not yet measured" note.
- /benchmarks shows each players' group's hardware split (RAM, VRAM, drive,
system, GPU kind) and, once the telemetry server has some, a "Players'
hardware" table from /v1/aggregate's breakdowns. Hidden without data.
- The picker takes the memory too. Players' groups whose installs have neither
the picked RAM nor the GPU's VRAM class count as further away, and the result
says what they had and when a game's peak memory is a large share of the RAM.
- Each GPU in the spec table has its memory (0: shared).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ThinkPad (i7-7500U, HD Graphics 620, Mesa): Horizon v2026.10.22.04 (two flights per scene) against vanilla
26.3 (two games) at render distance 12. Java loads chunks faster there and flies the mountain faster; the
page says so. Render distance 32 isn't published for it: neither game loaded the spawn in 5 minutes, and
Horizon kept only 900 to 1,400 columns resident when given 25.
- "Where Java is ahead" also lists scenes where vanilla's average beats Horizon's by more than 5%.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Three runs of each game at render distance 12 and 32 (tools/perf_bench.py, seed 1234, 1280x720, VSync off).
Horizon's average sits at the 144 Hz display (macOS presents in step with it even with VSync off): marked as
capped on the page.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ludovic Marie