Add MVP instructions on addressing benchmark comparison issues
Open
@oleksandr-pavlyk is already working on this.
Since Jul 17, 2026.
- Dominant language
- Cuda
- Stars
- 927
- Forks
- 123
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 2
Description
User has to know what to do with the errors that comparison script reported. If it's an ambiguous result, should they run again? Collect more data?
This issue can be closed by a PR that prints suggested steps in nvbench comparison script.
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.
Assessment
This issue has not been assessed yet.