Next, a more interesting test: editors. For terminal...

Next, a more interesting test: editors. For terminal editors I used Alacritty, and I've also added the fast and the slow baselines from the previous tests.

Here Neovim and Helix in text mode are the fastest, followed by nano, which has more spread for some reason. Next we have G-T-E and Builder with quite a bit of spread (@hergertme@fosstodon.org, any idea what's going on here?), then Helix and Neovim with IDE functionality, and finally VSCode.

2 years ago VSCode was better; maybe my extension setup changed

Box and scatter plot showing input latency for different editors.

Like 6 Aug 2023 at 12:13 | Open on mastodon.online

2 comments

Ivan Molodetskikh

Moar measurements: compositors. Since for this test the key presses are slow and there's no continuous redrawing, this should boil down to the amount of work a compositor does on screen update.

Un-vsynced X11 is obviously the fastest; thankfully work to add tearing flips to kernel and Wayland is ongoing.

Surprised to see GNOME Shell be a bit slower than raw Mutter, especially in fullscreen, since it doesn't really do much extra there. Extra surprised GNOME X11 is faster; might be noise.

Box and scatter plot of input latency against different compositors.

7 Aug 2023 at 11:21 | Open on mastodon.online

Ivan Molodetskikh

You might've heard that VTE got faster in GNOME 46. But how much faster?

I measured it with a hardware input latency tester! The answer is: *a lot* faster. Read all about it here: https://bxt.rs/blog/just-how-much-faster-are-the-gnome-46-terminals/

For anyone following along, this is also finally the blog post where I explain in some detail how the latency tester works and what is shown on the plots.

#gnome #gnome46 #terminal #linux #fedora

Input latency plot showing that GNOME 46 VTE terminals are almost on par with Alacritty now.

6 April at 9:12 | Open on mastodon.online