Calibrate benchmark files
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
Following up on https://github.com/nodejs/node/pull/59186 work.
Our benchmark suite takes a significant amount of time to conclude (85h for a full benchmark/compare). Most of the cases are because we are using an arbitrary n (number of iterations) in the benchmark, so it grows exponentially.
This issue is to keep tracking improvements from https://docs.google.com/spreadsheets/d/17iZuGR57r7ap4hFG8Tdz5Q-A7oV0cwM4MQW4q5bHA0U/edit?gid=2132828396#gid=2132828396
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
Start by reviewing the benchmark suite, the follow-up work in pull request #59186, and the linked tracking spreadsheet. Done means the affected benchmark cases have calibrated iteration counts and the resulting improvements are recorded in the spreadsheet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100