Summary:
`IVFPQSearchCagraConfig.lut_dtype` and `.internal_distance_dtype` are
typed as `cudaDataType_t` (a C enum from CUDA `<library_types.h>`).
Without an int typemap SWIG generates accessors that read/write a
`cudaDataType_t*` `SwigPyObject`, which Python users cannot construct,
so the fields are effectively read-only from Python:
```python
>>> import faiss
>>> c = faiss.IVFPQSearchCagraConfig()
>>> c.lut_dtype
<Swig Object of type 'cudaDataType_t *' at 0x...>
>>> c.lut_dtype = 2 # CUDA_R_16F
TypeError: in method 'IVFPQSearchCagraConfig_lut_dtype_set',
argument 2 of type 'cudaDataType_t'
>>> faiss.CUDA_R_16F # also not exported
AttributeError: module 'faiss' has no attribute 'CUDA_R_16F'
```
The doc comment on `IVFPQSearchCagraConfig.lut_dtype`
(`faiss/gpu/GpuIndexCagra.h`) recommends low-precision LUT for
large-dimension datasets — *"fast shared memory kernels can be used
even for datasets with large dimensionality"* — but the Python binding
does not let users act on that recommendation.
After this PR:
```python
c = faiss.IVFPQSearchCagraConfig()
c.lut_dtype = faiss.CUDA_R_16F # or CUDA_R_8U / CUDA_R_32F
c.internal_distance_dtype = faiss.CUDA_R_16F
```
The C++ ABI is unchanged; only the SWIG wrapper for these existing
fields changes. The typemap is added inside the `FAISS_ENABLE_CUVS`
block because that is where `cudaDataType_t` is referenced.
## Why it matters
`lut_dtype` controls whether cuVS' IVF-PQ `compute_similarity_kernel`
keeps the LUT in shared memory or falls back to a global-memory
variant. A quick before/after on an A10
(`MaxSharedMemoryPerBlockOptin = 99 KiB`) running the CAGRA build path
on a 768D / 1M-vector dataset (`pq_dim=192`, `pq_bits=8`):
| `lut_dtype` | LutT in kernel template | EnableSMemLut | Per-kernel duration |
|------------------------|-------------------------|---------------|---------------------|
| `CUDA_R_32F` (default) | `float` | 0 | 187 ms |
| `CUDA_R_16F` | `__half` | 0 | 166 ms |
| `CUDA_R_8U` | `fp_8bit<5, 1>` | **1** | **119 ms** |
End-to-end CAGRA `gpu_build` time on the same dataset goes from ~45 s
(default) to ~26 s (`CUDA_R_8U`). Recall@100 delta on the converted
HNSW index, normalized input, ef_search=100, 1000 queries:
−0.25 pp for fp8, +0.09 pp for fp16, both within run-to-run noise.
This is the lever the doc comment is pointing at; before this PR it
just was not reachable from Python.
Pull Request resolved: https://github.com/facebookresearch/faiss/pull/5191
Test Plan:
- New test: `faiss/gpu/test/test_lut_dtype_binding.py` (gated on
`"CUVS" in faiss.get_compile_options()`). 5 cases — constants
exported with the right values, default is `CUDA_R_32F`, set via
`faiss.CUDA_R_*`, set via raw int, and field independence. All pass
on a local `FAISS_ENABLE_CUVS=ON` build.
- Existing `faiss/gpu/test/test_cagra.py` (18) and
`faiss/gpu/test/test_binary_cagra.py` (4) unchanged, all pass.
- Sanity sweep on the patched build of `tests/test_factory.py +
test_index.py + test_index_accuracy.py + test_io.py +
test_product_quantizer.py + test_fast_scan.py +
test_fast_scan_ivf.py`: 407 pass, 1 unrelated skip, 0 fail.
## Out of scope
This PR does **not** change the C++ default of `lut_dtype`. cuVS' own
CAGRA wrapper (`cpp/include/cuvs/neighbors/graph_build_types.hpp`,
`cagra::graph_build_params::ivf_pq_params` constructor) defaults to
`CUDA_R_16F`, but aligning faiss with that default is a behaviour
change that deserves more cross-GPU and cross-dataset validation than
this PR carries. Best handled as a follow-up.
## Related
There is no prior issue or PR tracking this — searched the repository
issues, PRs, and the web. Happy to file a tracker issue if reviewers
prefer that pattern.
Reviewed By: mnorris11
Differential Revision: D104891046
Pulled By: bshethmeta
fbshipit-source-id: 96b550957fd01a8f2c249228b835ba7c42ef3abd
Faiss
Faiss is a library for efficient similarity search and clustering of dense vectors. It contains algorithms that search in sets of vectors of any size, up to ones that possibly do not fit in RAM. It also contains supporting code for evaluation and parameter tuning. Faiss is written in C++ with complete wrappers for Python/numpy. Some of the most useful algorithms are implemented on the GPU. It is developed primarily at Meta's Fundamental AI Research group.
News
See CHANGELOG.md for detailed information about latest features.
Introduction
Faiss contains several methods for similarity search. It assumes that the instances are represented as vectors and are identified by an integer, and that the vectors can be compared with L2 (Euclidean) distances or dot products. Vectors that are similar to a query vector are those that have the lowest L2 distance or the highest dot product with the query vector. It also supports cosine similarity, since this is a dot product on normalized vectors.
Some of the methods, like those based on binary vectors and compact quantization codes, solely use a compressed representation of the vectors and do not require to keep the original vectors. This generally comes at the cost of a less precise search but these methods can scale to billions of vectors in main memory on a single server. Other methods, like HNSW and NSG add an indexing structure on top of the raw vectors to make searching more efficient.
The GPU implementation can accept input from either CPU or GPU memory. On a server with GPUs, the GPU indexes can be used a drop-in replacement for the CPU indexes (e.g., replace IndexFlatL2 with GpuIndexFlatL2) and copies to/from GPU memory are handled automatically. Results will be faster however if both input and output remain resident on the GPU. Both single and multi-GPU usage is supported.
Installing
Faiss comes with precompiled libraries for Anaconda in Python, see faiss-cpu, faiss-gpu and faiss-gpu-cuvs. The library is mostly implemented in C++, the only dependency is a BLAS implementation. Optional GPU support is provided via CUDA or AMD ROCm, and the Python interface is also optional. The backend GPU implementations of NVIDIA cuVS can also be enabled optionally. It compiles with cmake. See INSTALL.md for details.
How Faiss works
Faiss is built around an index type that stores a set of vectors, and provides a function to search in them with L2 and/or dot product vector comparison. Some index types are simple baselines, such as exact search. Most of the available indexing structures correspond to various trade-offs with respect to
- search time
- search quality
- memory used per index vector
- training time
- adding time
- need for external data for unsupervised training
The optional GPU implementation provides what is likely (as of March 2017) the fastest exact and approximate (compressed-domain) nearest neighbor search implementation for high-dimensional vectors, fastest Lloyd's k-means, and fastest small k-selection algorithm known. The implementation is detailed here.
Full documentation of Faiss
The following are entry points for documentation:
- the full documentation can be found on the wiki page, including a tutorial, a FAQ and a troubleshooting section
- the doxygen documentation gives per-class information extracted from code comments
- to reproduce results from our research papers, Polysemous codes and Billion-scale similarity search with GPUs, refer to the benchmarks README. For Link and code: Fast indexing with graphs and compact regression codes, see the link_and_code README
Authors
The main authors of Faiss are:
- Hervé Jégou initiated the Faiss project and wrote its first implementation
- Matthijs Douze implemented most of the CPU Faiss
- Jeff Johnson implemented all of the GPU Faiss
- Lucas Hosseini implemented the binary indexes and the build system
- Chengqi Deng implemented NSG, NNdescent and much of the additive quantization code.
- Alexandr Guzhva many optimizations: SIMD, memory allocation and layout, fast decoding kernels for vector codecs, etc.
- Gergely Szilvasy build system, benchmarking framework.
Reference
References to cite when you use Faiss in a research paper:
@article{douze2024faiss,
title={The Faiss library},
author={Matthijs Douze and Alexandr Guzhva and Chengqi Deng and Jeff Johnson and Gergely Szilvasy and Pierre-Emmanuel Mazaré and Maria Lomeli and Lucas Hosseini and Hervé Jégou},
year={2024},
eprint={2401.08281},
archivePrefix={arXiv},
primaryClass={cs.LG}
}
For the GPU version of Faiss, please cite:
@article{johnson2019billion,
title={Billion-scale similarity search with {GPUs}},
author={Johnson, Jeff and Douze, Matthijs and J{\'e}gou, Herv{\'e}},
journal={IEEE Transactions on Big Data},
volume={7},
number={3},
pages={535--547},
year={2019},
publisher={IEEE}
}
Join the Faiss community
For public discussion of Faiss or for questions, visit https://github.com/facebookresearch/faiss/discussions.
We monitor the issues page of the repository. You can report bugs, ask questions, etc.
Legal
Faiss is MIT-licensed, refer to the LICENSE file in the top level directory.
Copyright © Meta Platforms, Inc.