ru it vacancy extractor qwen3 1.7b needs about 2.5 GB of memory at Q4_K_M (a 1.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 2 quants, from 1.1 GB (Q4_K_M) to 1.8 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.
Qwen3-1.7B model for extracting IT vacancy fields in Russian
The model extracts structured data from Russian IT vacancy texts. It outputs a JSON object with role, grade, skills, salary, work format, cities, experience, employment type, and language. The model is based on Qwen3-1.7B and fine‑tuned with LoRA.
Good at
- Structured extraction from Russian text
- JSON output for downstream use
- Handles multiple job fields
Limits
- No vision support
- License type is other
- Context length limited to 40960 tokens
Best for
- Building job boards
- Automating resume parsing
- Creating structured job datasets
Who it’s for. Developers and data scientists building job‑listing platforms or analytics tools that require accurate extraction of job attributes from Russian IT vacancy posts. The model is suitable for integration into pipelines that need structured JSON output.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 1.1 GB | 2.5 GB | Fits | Get file → | |
| Q8_0 | 1.8 GB | 3.3 GB | Fits | Get file → |
For 8 GB VRAM use the Q4_K_M quant (1.11 GB file, ~2.5 GB memory at 8 k context). For 12 GB VRAM the Q8_0 quant (1.83 GB file, ~3.3 GB memory) provides higher precision. Estimates are approximate.
What GPU do you need for ru it vacancy extractor qwen3 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 (1.8 GB file, about 3.3 GB in use).
Which ru it vacancy extractor qwen3 1.7b quant should you choose?
Q4_K_M is the usual starting point for ru it vacancy extractor qwen3 1.7b: it balances file size and quality well. Here it is a 1.1 GB file.
The Q8_0 file is 1.8 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 ru it vacancy extractor qwen3 1.7b
How much VRAM does ru it vacancy extractor qwen3 1.7b need?
About 2.5 GB at Q4_K_M with an 8K context window. That is the 1.1 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 ru it vacancy extractor qwen3 1.7b on an 8 GB GPU?
Yes, with Q8_0: the 1.8 GB file needs about 3.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of ru it vacancy extractor qwen3 1.7b GGUF?
It depends on the quant: Q4_K_M is 1.1 GB, Q8_0 is 1.8 GB.
What context length does ru it vacancy extractor qwen3 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 ru it vacancy extractor qwen3 1.7b GGUF?
The files are on Hugging Face in the alekseevpavel04/ru-it-vacancy-extractor-qwen3-1.7b repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does ru it vacancy extractor qwen3 1.7b use?
Hugging Face lists the license as other. 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 this model on 8 GB VRAM?
Yes, using the Q4_K_M quant file (1.11 GB) which requires about 2.5 GB of VRAM at 8 k context.
Does the model support English text?
The model is fine‑tuned for Russian IT vacancy text and may not reliably extract English job postings.
What context length does it support?
The model supports up to 40960 tokens of context, as specified in its training configuration.