Add local Qwen3 embedding benchmark matrix - #3
Open
CompleteDotTech wants to merge 5 commits into
Open
Conversation
This was referenced Sep 3, 2026
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.
What
Why
Unstract already supports local vector databases and OpenAI-compatible embedding endpoints, but it did not provide local model-serving containers or a repeatable CPU/GPU comparison matrix. This keeps all six variants available for the benchmark review; unselected variants are intentionally not removed in this PR.
How
The Compose include is profile-gated, so the normal development stack does not download model weights. The services expose TEI's OpenAI-compatible endpoint and share the existing Unstract network.
Published benchmark snapshot
The following is the published MTEB comparison shown in the Qwen model cards, not a measurement from this checkout. The card labels this as an MTEB online snapshot dated 2025-05-24.
Sources: Qwen3-Embedding-0.6B, Qwen3-Embedding-4B, and Qwen3-Embedding-8B model cards. The official MTEB page for 4B lists approximately 7.5 GB model memory and the 8B page lists approximately 14.1 GB; actual service memory also depends on runtime, batch limits, and sequence lengths.
Can this PR break any existing features. If yes, please list possible items. If no, please explain why.
The default stack behavior is unchanged because all six embedding services are profile-gated. The OpenAI-compatible adapter keeps its existing defaults when prefixes are blank. A model change still requires a separate vector collection and full reindex when dimensions differ.
Potential operational impact: starting embeddings-both can exceed one GPU's memory, and first startup downloads large model artifacts into persistent volumes.
Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Screenshots
Not applicable.
Checklist
I have read and understood the Contribution Guidelines.