-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FAISS with cuVS enabled in cuvs-bench #561
base: branch-25.02
Are you sure you want to change the base?
Conversation
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here are couple suggestions on my side to keep the faiss behavior in line with other algorithms.
@@ -484,6 +484,7 @@ void register_search(std::shared_ptr<const dataset<T>> dataset, | |||
->UseRealTime(); | |||
|
|||
if (metric_objective == Mode::kThroughput) { b->ThreadRange(threads[0], threads[1]); } | |||
if (metric_objective == Mode::kThroughput) { b->ThreadRange(threads[0], threads[1]); } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess, this can be removed now?
if (metric_objective == Mode::kThroughput) { b->ThreadRange(threads[0], threads[1]); } |
Mostly adapted from rapidsai/raft#2026