microsoft / microsoft/terminal
[Performance] vtebench tracking issue
Open
Nobody has claimed this yet.
Area-Performance
Issue-Feature
Product-Meta
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
This is an attempt to use vtebench by alacritty to measure & establish the performance baseline of Windows Terminal.
The program itself requires bash so we can only test it through WSL and SSH. Still it shows the real-life performance of this product.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files or tests. Start by reading the vtebench project and determine how it can be run through WSL and SSH; done means establishing a Windows Terminal performance baseline using that benchmark.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, cpp
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100