You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
vamshin
changed the title
[FEATURE] Switch default engine from nmslib to faiss
[FEATURE] Switch default vector engine from nmslib to faiss
Sep 27, 2024
I think that until we can automatically handle cases where the data may not fit inside fp_16, we should not do this yet. Instead, for OOTB experience, users can specify compression and/or mode. If needed, we can introduce a new mode or similar meta parameter.
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.
The text was updated successfully, but these errors were encountered: