qmd query expansion 1.7B needs about 2.7 GB of memory at Q4_K_M (a 1.3 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 4 quants, from 1.3 GB (Q4_K_M) to 4.1 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.
QMD Query Expansion 1.7B – a fine‑tuned Qwen3 model for structured search query expansion
QMD Query Expansion 1.7B is a 1.7 B parameter model based on Qwen3‑1.7B. It is trained to produce structured expansions for search queries, outputting lines prefixed with lex:, vec:, or hyde:. The model supports a 32,768 token context length and is released under the MIT license.
Good at
- Structured query expansion for hybrid retrieval
- Outputting lex:/vec:/hyde: formatted lines
- Fine‑tuned for search‑specific language
Limits
- No vision or multimodal support
- Requires 8‑k context for memory estimates
- No explicit multilingual capability listed
Best for
- Search engine query expansion pipelines
- Hybrid retrieval systems needing structured outputs
- Training data augmentation for retrieval models
Who it’s for. Developers building or maintaining hybrid search systems that need concise, structured query expansions. The model is useful for teams that require a lightweight, open‑source solution for generating lex, vec, and hyde outputs.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 1.3 GB | 2.7 GB | Fits | Get file → | |
| Q5_K_M | 1.5 GB | 2.9 GB | Fits | Get file → | |
| Q8_0 | 2.2 GB | 3.6 GB | Fits | Get file → | |
| F16 | 4.1 GB | 5.5 GB | Fits | Get file → |
For 8 GB VRAM use Q4_K_M (1.28 GB, ~2.7 GB RAM). For 16 GB VRAM Q5_K_M (1.47 GB, ~2.9 GB RAM) or Q8_0 (2.17 GB, ~3.6 GB RAM). F16 (4.07 GB, ~5.5 GB RAM) requires larger memory budgets.
What GPU do you need for qmd query expansion 1.7B?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is Q8_0 (2.2 GB file, about 3.6 GB in use).
- 6 GB VRAM: the best quant that fits is F16 (4.1 GB file, about 5.5 GB in use).
Which qmd query expansion 1.7B quant should you choose?
Q4_K_M is the usual starting point for qmd query expansion 1.7B: it balances file size and quality well. Here it is a 1.3 GB file.
The Q8_0 file is 2.2 GB, about 1.7 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about qmd query expansion 1.7B
How much VRAM does qmd query expansion 1.7B need?
About 2.7 GB at Q4_K_M with an 8K context window. That is the 1.3 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run qmd query expansion 1.7B on an 8 GB GPU?
Yes, with F16: the 4.1 GB file needs about 5.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of qmd query expansion 1.7B GGUF?
It depends on the quant: Q4_K_M is 1.3 GB, Q5_K_M is 1.5 GB, Q8_0 is 2.2 GB, F16 is 4.1 GB.
What context length does qmd query expansion 1.7B support?
The GGUF header lists a trained context length of 40,960 tokens (40K). The KV cache grows with the context you use: about 0.9 GB at 8K and 3.8 GB at 32K.
Where can I download qmd query expansion 1.7B GGUF?
The files are on Hugging Face in the tobil/qmd-query-expansion-1.7B-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does qmd query expansion 1.7B use?
Hugging Face lists the license as mit. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run QMD Query Expansion 1.7B on 8 GB VRAM?
Yes, the Q4_K_M quantization uses about 1.28 GB file size and requires roughly 2.7 GB RAM at 8 k context, fitting within an 8 GB VRAM budget.
Does the model support multilingual queries?
The base Qwen3 model supports many languages, but the fine‑tuned query expansion model has no explicit multilingual capability listed.
Is the model licensed for commercial use?
It is released under the MIT license, allowing commercial use with attribution.