Add benchmark with realistic escape sequence frequency #40
Comments
chrisduerr
added a commit
to chrisduerr/vtebench
that referenced
this issue
Dec 20, 2024
This patch adds a new benchmark which aims at filling a gap between the `dense_cells` and the `light_cells` benchmarks, providing a more realistic example of escape sequence density in a normal terminal workflow. The new benchmark is an Alacritty ref test recording of a short NeoVim session, which includes several small and large buffer movements, different styles of underlines, and window-in-window using a fuzzy finder and tiled buffers. This new test intentionally uses a workflow that is pretty escape sequence heavy, while still being realistic, since workflows without heavy escape sequence use are already reasonably well covered by the `light_cells` benchmark. Closes alacritty#40.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we have only extremely focused benchmarks.
dense_cellstests a scenario where every single cell takes a huge escape sequence, whilelight_cellstests for scenarios where pretty much no escape sequences are present.When it comes to improving performance with something like alacritty/alacritty#8347, it's not always possible to improve every individual component of the parser. Since the "medium workload" in between
dense_cellsandlight_cellsis likely the best representation of what users would encounter in the real world, it should make sense to add this extra benchmark as a hint at real-world performance.Generally speaking this is likely best simulated by an escape sequence heavy application, that doesn't just focus on generating graphical effects (like
mpv -vo tct). The best choice that comes to my mind would be vim with a workflow that includes both local edits, complete buffer jumps, and popups like fuzzy finders.The text was updated successfully, but these errors were encountered: