mirror of
https://github.com/kovidgoyal/kitty
synced 2026-07-23 00:38:10 +02:00
Finally got gnome-terminal to run on my system
Apparently it needed some kind of GTK desktop portal or the other
🙄
Interesting that its numbers are basically the same as alacritty's. Lot
better than I remember, I guess the recent libvte performance work was
good.
This commit is contained in:
@@ -65,6 +65,7 @@ as fast as the next best.
|
|||||||
Terminal ASCII Unicode CSI Images Average
|
Terminal ASCII Unicode CSI Images Average
|
||||||
================ ====== ======= ===== ====== =======
|
================ ====== ======= ===== ====== =======
|
||||||
kitty 0.33 117.7 104.0 59.3 249.7 132.68
|
kitty 0.33 117.7 104.0 59.3 249.7 132.68
|
||||||
|
gnometerm 3.50.1 33.4 55.0 16.1 142.8 61.83
|
||||||
alacritty 0.13.1 43.1 46.5 32.5 94.1 54.05
|
alacritty 0.13.1 43.1 46.5 32.5 94.1 54.05
|
||||||
wezterm 20230712 16.4 26.0 11.1 140.5 48.5
|
wezterm 20230712 16.4 26.0 11.1 140.5 48.5
|
||||||
xterm 389 47.7 18.3 0.6 56.3 30.72
|
xterm 389 47.7 18.3 0.6 56.3 30.72
|
||||||
@@ -78,27 +79,28 @@ ASCII only text.
|
|||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
By default, the benchmark kitten suppresses actual rendering, to better focus
|
By default, the benchmark kitten suppresses actual rendering, to better
|
||||||
on parser speed, you can pass it the ``--render`` flag to not suppress
|
focus on parser speed, you can pass it the ``--render`` flag to not suppress
|
||||||
rendering. However, modern terminals typically render asynchronously,
|
rendering. However, modern terminals typically render asynchronously,
|
||||||
therefore the numbers are not really useful for comparison. However, even
|
therefore the numbers are not really useful for comparison, as it is just a
|
||||||
with rendering enabled kitty is still much faster than all the rest. For
|
game about how much input to *batch* before rendering the next frame.
|
||||||
brevity those numbers are not included.
|
However, even with rendering enabled kitty is still faster than all the
|
||||||
|
rest. For brevity those numbers are not included.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
gnome-terminal is left out as I could not get it to start on my system and
|
foot, iterm2 and Terminal.app are left out as they do not run under X11.
|
||||||
foot is left out as it does not run under X11. Alacritty+tmux is included
|
Alacritty+tmux is included just to show the effect of putting a terminal
|
||||||
just to show the effect of putting a terminal multiplexer into the mix
|
multiplexer into the mix (halving throughput) and because alacritty isnt
|
||||||
(halving throughput) and because alacritty isnt really comparable to any of
|
remotely comparable to any of the other terminals feature wise without tmux.
|
||||||
the other terminals feature wise without tmux.
|
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
konsole and xterm dont support the `Synchronized update
|
konsole, gnome-terminal and xterm do not support the `Synchronized update
|
||||||
<https://gitlab.com/gnachman/iterm2/-/wikis/synchronized-updates-spec>`__
|
<https://gitlab.com/gnachman/iterm2/-/wikis/synchronized-updates-spec>`__
|
||||||
escape code used to suppress rendering, if and when they gain support for it
|
escape code used to suppress rendering, if and when they gain support for it
|
||||||
their numbers are likely to improve by ``20 - 30%``.
|
their numbers are likely to improve by ``20 - 50%``, depending on how well they
|
||||||
|
implement it.
|
||||||
|
|
||||||
|
|
||||||
Energy usage
|
Energy usage
|
||||||
|
|||||||
Reference in New Issue
Block a user