is cubql using rtx?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 89
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Disclaimer: there is a lot of gap in my knowledge about this question.
Context: In the past I was using Optix for nearest neighbor search (I promise that in my context using raycasting for approximate nearest neighbor was not as dumb as it sounds), then migrated to cubql for various reasons. This is a shared GPU on a robot, so there are mild real time constraints and GPU sharing issues.
My understanding is that Optix makes use of RTX, and that Optix under the hood builds a BVH just like cuBQL. So I was wondering whether cuBQL used RTX too.
When I used Optix instead of cuBQL, one benefit was that on our shared GPU my process was the only process using RTX, and therefore it was not conflicting with anything else. After switching to cuBQL, it seems that we have a bit more conflicts.
Does that make sense? Also is RTX used for the BVH building step or the query step or both?
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 by tracing cuBQL's BVH build and query paths and comparing them with OptiX's RTX behavior. Verify whether either path uses RTX and document the answer, including GPU-sharing implications; the issue names no repository files or tests, so maintainers would need to point to entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100