Measured performance

AMD Ryzen AI 9 365 / Linux. Timings are medians in milliseconds; lower is better.

Ready to edit

These measurements compare editing readiness with isolated configurations and LSP disabled. They do not compare equivalent feature setups: Runyte includes integrated terminals, Git workflows, and persistent sessions, while other editors provide different combinations of built-in features and plugins. Results do not predict performance with your configuration.

Time from launch to a visible edit, with warm caches and LSP disabled. Initial syntax parsing may still be running. Ten measured launches per cell follow one warm-up; every sample passes whole-file save verification.

30 September 2026 · Runyte v0.3.5 (b937570) · Neovim 0.12.5 · Helix 25.07.1

FileLinesNeovimHelixRunyte
Text50020.932.218.8
Text5,00020.932.720.4
Text50,00022.633.026.9
Text500,00038.645.988.0
Lua50042.339.120.6
Lua5,00031.763.721.7
Lua50,00031.3349.027.9
Lua500,00045.7548.8102.5

Detailed results and methodology on GitHub

Persistent sessions

Runyte time to visible output, median of three samples per scenario.

30 September 2026 · Runyte v0.3.5 (b937570)

ScenarioCold startWarm attach
One session34.236.12
Three sessions33.266.80
Three sessions, strip hidden34.046.27
Three sessions, another terminal producing output33.436.70

Session results and methodology on GitHub

Quit and idle

Quit medians use ten launches. Idle uses five ten-second windows with a 5,000-line Lua file open in a Git repository.

30 September 2026 · Runyte v0.3.5 (b937570)

MeasurementRunyte
Quit immediately after first document frame, 50,000-line Lua4.9 ms
Quit after settling, 50,000-line text4 ms
Quit after settling, 50,000-line Lua22 ms
Idle CPU, median0.00%
Idle screen writes0

Quit and idle results and methodology on GitHub

All benchmark harnesses · Finder vs. fzf