Commit Graph

2 Commits (main)

Author SHA1 Message Date
Tarang Jain cd797c7c38 Benchmarking Scripts for cuVS Index, more docs updates (#4117)
Summary:
- Small updates to FAISS + cuVS docs.
- Fixes IVF-Flat and IVF-PQ benchmarking scripts.
- Re-enable cuVS backend in gpu python tests

Pull Request resolved: https://github.com/facebookresearch/faiss/pull/4117

Reviewed By: mnorris11

Differential Revision: D68792968

Pulled By: asadoughi

fbshipit-source-id: 36cd0bbd51635bc559144e9d5733dc29e6f7a229
2025-01-28 17:11:18 -08:00
Tarang Jain 134922061c Migrate from RAFT to CUVS (#3549)
Summary:
Remove the dependency on `raft::compiled` and modify GPU implementations to use cuVS backend in place of RAFT.

A deeper insight into the dependency:
FAISS gets the ANN algorithm implementations such as IVF-Flat and IVF-PQ from cuVS. RAFT is meant to be a lightweight C++ header-only template library that cuVS relies on for the more fundamental / low-level utilities. Some examples of these are RAFT's device mdarray and mdspan objects; the RAFT resource object (`raft::resource`) that takes care of the stream ordering of device functions; linear algebra functions such as mapping, reduction, BLAS routines etc. A lot of the cuVS functions take the RAFT mdspan objects as arguments (for example `raft::device_matrix_view`). Therefore FAISS relies on both cuVS and RAFT. FAISS gets RAFT headers through cuVS and uses them to create the function arguments that can be consumed by cuVS. Note that we are not explicitly linking FAISS against `raft::raft` or `raft::compiled`. Only the required headers are included and compiled rather than compiling the whole RAFT shared library. This is the reason we still see mentions of `raft` in FAISS.

Pull Request resolved: https://github.com/facebookresearch/faiss/pull/3549

Reviewed By: ramilbakhshyiev

Differential Revision: D62041013

Pulled By: asadoughi

fbshipit-source-id: 7230dcc06cf47baf95873adc1dec2adca4a8f82a
2024-11-14 11:30:16 -08:00