Tracking `nvbench` benchmark results
Open
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 927
- Forks
- 123
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 2
Description
Is there any interest in tracking the results from nvbench?
I'm considering adding an adapter for nvbench to my continuous benchmarking tool, Bencher: https://github.com/bencherdev/bencher
And I figured I should check in on whether there is already a preferred way to do this.
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.
Research direction
The issue names no files, tests, or entry points. First determine whether nvbench has a preferred mechanism for tracking results and clarify the desired relationship with Bencher; the work is done when an agreed integration scope and implementation path are defined.
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