[FEA] Improvements to benchmarking methodology in the docs
@aamijar is already working on this.
Since Feb 26, 2026.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
The following feedback was given about our benchmarking methodology page in the docs. We should strive to improve these docs so they are more clear and easier to understand.
-
Pls define exact vs. actual nearest neighbors. Is exact the set known by an oracle, e.g. with exhaustive search, and actual is what the heuristic search yielded?
-
The (intersection of 2 sets of K)/K method evaluates wrt the exact set, but other recall evaluation methods consider whether you're within a given convergence threshold, correct? What's that called, and is that relevant enough to bring up here?
-
Meaning of grey line isn't clear, or why green lines don't go all the way to 1
-
Bucket list shows 85% but graph shows 80%
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.
Assessment
This issue has not been assessed yet.