Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Control over GPU <-> CPU result copies? #45

Open
lumost opened this issue Sep 23, 2021 · 1 comment
Open

Control over GPU <-> CPU result copies? #45

lumost opened this issue Sep 23, 2021 · 1 comment

Comments

@lumost
Copy link

lumost commented Sep 23, 2021

is it possible to control whether the results from a given GPU search are CPU/Host memory resident or GPU memory resident?

@Enet4
Copy link
Owner

Enet4 commented Oct 5, 2021

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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants