-
Notifications
You must be signed in to change notification settings - Fork 34
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
Control over GPU <-> CPU result copies? #45
Comments
This is an intriguing question. These bindings are implemented through the C API, which in turn uses the native C++ API. To the best of my knowledge, the high level API here does not provide that sort of awareness. If you can provide an example of how this would be done in C++ through the main Faiss API, then we may have a clearer idea of how this could be achieved in Rust. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
is it possible to control whether the results from a given GPU search are CPU/Host memory resident or GPU memory resident?
The text was updated successfully, but these errors were encountered: