Skip to content
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

Switch default vector engine from nmslib to faiss #2163

Open
vamshin opened this issue Sep 27, 2024 · 3 comments
Open

Switch default vector engine from nmslib to faiss #2163

vamshin opened this issue Sep 27, 2024 · 3 comments

Comments

@vamshin
Copy link
Member

vamshin commented Sep 27, 2024

Is your feature request related to a problem?
The nmslib vector engine is currently in maintenance mode as of 10/27, and we plan to deprecate it in the 3.x version. All the feature development/optimizations are focused in faiss engine since 2.7 version. To align the new vector indexes with these improvements, it would be beneficial to switch the default vector engine from nmslib to faiss.

What solution would you like?
Switch the default vector engine from nmslib to faiss.

@vamshin vamshin changed the title [FEATURE] Switch default engine from nmslib to faiss [FEATURE] Switch default vector engine from nmslib to faiss Sep 27, 2024
@vamshin vamshin added v2.18.0 Roadmap:Vector Database/GenAI Project-wide roadmap label and removed untriaged labels Sep 27, 2024
@vamshin vamshin changed the title [FEATURE] Switch default vector engine from nmslib to faiss Switch default vector engine from nmslib to faiss Sep 27, 2024
@navneet1v
Copy link
Collaborator

@vamshin I see this issue is put in 2.18 version? is the feature planned for 2.18?

@vamshin
Copy link
Member Author

vamshin commented Oct 2, 2024

@navneet1v yes, idea is to do for 2.18

@vamshin
Copy link
Member Author

vamshin commented Oct 7, 2024

As part of this default switch to faiss, I feel we should also switch to fp_16 with in faiss.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New
Status: 2.18.0
Development

No branches or pull requests

2 participants