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

Use b1 quantization for USearch #2644

Merged
merged 1 commit into from
May 14, 2024
Merged

Conversation

ashvardanian
Copy link
Contributor

As suggested by @adolfogc (in unum-cloud/usearch#405) the USearch implementation should use b1 instead of i8 for binary representations.

As suggested by @adolfogc (in unum-cloud/usearch#405)
the USearch implementation should use `b1` instead of `i8`
for binary representations.
@tomaarsen
Copy link
Collaborator

Hello!

Looks good to me, I trust the expert on this one! Also, keep up the good work, and apologies that the NLTK StringZilla work hasn't moved forward yet - I don't really have time for that project anymore sadly.

  • Tom Aarsen

@tomaarsen tomaarsen merged commit 90171f5 into UKPLab:master May 14, 2024
9 checks passed
@ashvardanian
Copy link
Contributor Author

I trust the expert on this one!

Haha, I wouldn't - let's check that CI passes, if you have some 😅


As for NLTK, I'm prepping more improvements for StringZilla with more incoming contributors. NLTK still seems like a good place to apply those optimizations, so if you'd know someone who can validate the suggestions - happy to connect 🤗

@tomaarsen
Copy link
Collaborator

I'm afraid I don't have CI over the semantic search examples 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants