Minimal viable benchmarks
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
Following the discussion during the first meeting of the team a few topics were raised regarding benchmarks
- how we want to benchmark the runtime
- what should we benchmark
Some issues were also discussed about benchmarks
- time to run all benchmark
- in which architecture
- how frequently
I will grab and put the discussion we had yesterday (at least the key points made) so we can have a constructive talk around it
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 with the meeting discussion and key points referenced in the issue. Use them to clarify the runtime benchmarks, benchmark scope, acceptable full-suite duration, target architectures, and execution frequency; the issue is done when these decisions are documented as an agreed benchmark plan.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100