[rush] Add auditing in rushstack CI/CD to catch performance regressions
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- nodejs, typescript
- Domain
- ci-cd, performance, tooling
Research direction
Start by reviewing the related concept in issue #5690 and the proposed Rush scenarios: rush --help, rush check, rush change --no-fetch --verify, and an already-installed rush install. Done means benchmark data is generated, a main-branch reference is maintained, and PR CI compares results to identify regressions or improvements.
Written by the indexing model from the issue text.
Description
Summary
We should add a benchmark test project that runs various common scenarios for Rush, leveraging V8 code coverage to collect information on:
| item | unit | source |
|---|---|---|
| Executed Code | KiB | V8 Code Coverage |
| Unused Code | KiB | V8 Code Coverage |
| Loaded Code | KiB | V8 Code Coverage |
| Loaded Files | # | V8 Code Coverage |
| Duration | ms | time / cpuprofile |
Once we have this data being generated, we should have a baseline CI pipeline that calculates a new reference value for every commit into main, and then have the PR CI job do performance comparisons and look for regressions/improvements. This will help us catch performance regressions and give us a standard for evaluating impact of optimizations.
This is the same concept as #5690 , but targeting @microsoft/rush.
Candidates for benchmarking:
rush --helprush checkrush change --no-fetch --verify(--no-fetchis important to avoid externalities, and should really be the default)rush install(after having already installed, we're checking the "nothing to do" state)
- Dominant language
- TypeScript
- Stars
- 6.5k
- Forks
- 708
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 48
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoft/rushstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in microsoft/rushstack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·