[ENHANCEMENT]: Perf guide
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 667
- Forks
- 120
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
cuCollections exposes a set of knobs that allow optimizing a hashing data structure for a specific use case.
For example:
- which probing scheme should I use?
- what's the best CG size?
- how does the input data type affect performance?
- can I use particular operations concurrently? How does that impact performance?
The interaction between those choices is also non-trivial.
Finding out which combination works best for an application is a time-consuming task.
Describe the solution you'd like
Write a perf guide. Could be as simple as a Markdown file.
Describe alternatives you've considered
No response
Additional context
No response
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
No file or test is named. Start by reviewing cuCollections' hashing data structure options and the performance questions listed in the issue, then identify how probing, CG size, input type, and concurrency interact. Done means a Markdown performance guide that explains those choices and how users can evaluate combinations for their applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100