Add support for evaluating reduced-dimension (Matryoshka) embeddings - #7
Open
Andrian0s wants to merge 1 commit into
Open
Add support for evaluating reduced-dimension (Matryoshka) embeddings#7Andrian0s wants to merge 1 commit into
Andrian0s wants to merge 1 commit into
Conversation
…sier examine efficiency performance tradeoffs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #6
Summary
This PR adds the possibility to evaluate embedding models with reduced dimensions (Matryoshka), implemented as a truncation on the embeddings. It lets users easily check whether their domain would see a significant performance drop from using dimensionality-reduced embeddings.
What changed
Notes
The dimensionality reduction is a plain truncation of the embedding vectors, as used in Matryoshka representation learning.
Not all models "guarantee" matryoshka representation learning dimensionality reduction results but other models won't break with this addition either, they will just underperform which the user should understand. No need to handle any form of "checks" before running with the truncation
Should work as expected but I recommend the maintainers to ensure that nothing broke from these minimal additions.