NVIDIA / NVIDIA/cuvs

[FEA] Improvements to benchmarking methodology in the docs

Open
#1,854 1 comment 0 reactions 1 assignee View on GitHub

@aamijar is already working on this.

Since Feb 26, 2026.

feature request
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.

  1. 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?

  2. 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?

  3. Meaning of grey line isn't clear, or why green lines don't go all the way to 1

  4. Bucket list shows 85% but graph shows 80%

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.