mirror of
https://codeberg.org/dnkl/foot.git
synced 2026-03-13 05:33:51 -04:00
doc: benchmark: move alacritty-unicode-random text from footnote to separate chapter
This commit is contained in:
parent
ae75a7933f
commit
8524e32bd5
1 changed files with 20 additions and 13 deletions
|
|
@ -81,17 +81,24 @@ Scrollback=10000 lines
|
||||||
| scrolling-filled-lines | 1.888s ±0.021 | 2.334s ±0.078 | 2.145s ±0.074 | 3.372s ±0.078 | 2.144s ±0.091 |
|
| scrolling-filled-lines | 1.888s ±0.021 | 2.334s ±0.078 | 2.145s ±0.074 | 3.372s ±0.078 | 2.144s ±0.091 |
|
||||||
| unicode-random | 1.545s ±0.229 | 0.164s ±0.012 [^1] | 11.180s ±0.342 | crashed | 11.389s ±0.269 |
|
| unicode-random | 1.545s ±0.229 | 0.164s ±0.012 [^1] | 11.180s ±0.342 | crashed | 11.389s ±0.269 |
|
||||||
|
|
||||||
|
[^1]: [Alacritty and "unicode-random"](#alacritty-and-unicode-random)
|
||||||
|
|
||||||
[^1]: Alacritty is actually **really** slow at rendering this (whether
|
|
||||||
it is fallback fonts in general, emojis, or something else, I
|
# Alacritty and "unicode-random"
|
||||||
don't know). I believe the reason it finishes the benchmark so
|
|
||||||
quickly is because it reads from the PTY in a separate thread,
|
Alacritty is actually **really** slow at rendering this (whether it is
|
||||||
into a larger receive buffer which is then consumed by the main
|
fallback fonts in general, emojis, or something else, I don't know).
|
||||||
thread. This allows the client program to write its output much
|
|
||||||
faster since it is no longer stalling on a blocked PTY. This means
|
I believe the reason it finishes the benchmark so quickly is because
|
||||||
Alacritty only needs to render a couple of frames since it can
|
it reads from the PTY in a separate thread, into a larger receive
|
||||||
reach the final VT state almost immediately. On the other hand,
|
buffer which is then consumed by the main thread. This allows the
|
||||||
`cat`:ing the `unicode-random` test file in an endless loop, or
|
client program to write its output much faster since it is no longer
|
||||||
just manually scrolling up after the benchmark is done is
|
stalling on a blocked PTY.
|
||||||
**slow**, which besides being felt (input lag), can be seen by
|
|
||||||
setting `debug.render_timer = true` in `alacritty.yml`.
|
This means Alacritty only needs to render a couple of frames since it
|
||||||
|
can reach the final VT state almost immediately.
|
||||||
|
|
||||||
|
On the other hand, `cat`:ing the `unicode-random` test file in an
|
||||||
|
endless loop, or just manually scrolling up after the benchmark is
|
||||||
|
done is **slow**, which besides being felt (input lag), can be seen by
|
||||||
|
setting `debug.render_timer = true` in `alacritty.yml`.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue