[FEA] consider separating configs for cuda ann-benchmarks into different directories based on algorithm
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 1k
- Forks
- 251
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
I think this will make the configs much easier to manage overall, especially since we are breaking the benchmarks out into separate executables/targets to parallelize the builds and match the build design of the googletests/prims benchmarks more consistently.
I suppose in a way it could also make them harder to manage since it becomes a little harder to compare algorithm parameters side by side, but I think this might not be that bad overall.
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
Start by locating the CUDA ann-benchmark configuration directories and the existing executable or target definitions mentioned in the issue. Compare them with the googletests and prims benchmark layouts, then define separate algorithm-based config directories and confirm that the parallelized targets still use the intended parameters.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100