I have updated termbench to v2. It now attempts to run four standard tests and provide a composite number. This version is also designed to be compilable on Linux and Mac, although it needs more testing on those platforms:https://github.com/cmuratori/termbench …
-
Show this thread
-
Replying to @cmuratori
Oh boy. None of my terminals here (gnome-terminal, konsole, xterm, rxvt) qualify as "reasonably fast" by that metric :( xterm is thoroughly disappointing; mrxvt is fast, but displays the attribute test incorrectly; the "big" desktops' terminals are meh. (clang 10.0.0, -O3)pic.twitter.com/06BPhe25ag
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @BenchmarkPoof @KeyJ_trbl
At some point I need to put out a video explaining that there are many sources of slow-down here, on both Windows and Linux. I think the conhost/cmd.exe/terminal message got out on Windows but I don't think some of the Linux users understand a similar thing happens on Linux?
1 reply 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @BenchmarkPoof @KeyJ_trbl
Well, I specifically say in the readme that I have do not have any Linux investigations yet. But the kernel isn't the only bottleneck here, because if it was, you wouldn't have such widely varying speeds on Linux. Alacritty wouldn't be faster than xterm, etc., but it is.
2 replies 0 retweets 1 like
That said, I made refterm + termbench specifically to determine what was slow in Windows, and I think we pretty much have that figured out now. Unfortunately, until someone makes a refterm-equivalent for Linux, it will be hard to do the same level of investigation.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.