How fast should an unoptimized terminal run?

• Windows Terminal

  506 93,573 9.7 C++

  The new Windows Terminal and the original Windows console host, all in the same place!

  

Also mmozeiko, in the original github issue that spawned this whole thing, identified that the issue in conhost is that it does a bunch of unnecessary string processing that is slow. So, on some level, Casey does know why conhost is slow, because he read that thread.

• refterm

  37 1,496 0.0 C

  Reference monospace terminal renderer

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• hyperterm

  85 42,656 9.6 TypeScript

  A terminal built on web technologies

  

• termbench

  9 203 1.9 C++

  Simple benchmark for terminal output

When looking into the issue further, he made a benchmark for the terminal: termbench. On the issue he made, him and a couple others found that the Windows Terminal was spending a large amount of time parsing VT codes. A fair bit of this bottleneck was due to std::string and std::vector resizing.

Suggest a related project