3 ms·
I am interested in testing this in production, instead of faiss/mrpt. > metric='cos', # Choose 'l2sq', 'haversine' or other metric, default = 'ip' As a note,
by freediver 3y ago
I am interested in testing this in production, instead of faiss/mrpt.
> metric='cos', # Choose 'l2sq', 'haversine' or other metric, default = 'ip'
As a note, it is actually 'l2_sq' for the Python example.
> index.add(labels=np.arange(len(vectors)), vectors=vectors)
Adding to index appears to be very slow. Also labels are listed as an optional param but the Python SDK has them as required.
Do you have setup of params for 'brute force' approach (100% accuracy)?
- ashvardanian 3y agoSure! You can pass exact=True to the search interface. > Adding to index appears to be very slow. Interesting. Can you please elaborate? We benchmark it on daily basis, but there is always a chance we forgot some corner case :) PS: Thanks for considering us! USearch is already used in production by a few companies (small and very large), and we would be happy to assist with integration! PS2: Argument name inconsistency is solved on the main-dev, and will be released with a bunch of major changes in 1.0 this week.