Xing4.0 29B-A4B
29B-A4BA 29B mixture-of-experts text model from XingChen-AGI under Apache 2.0 that reads about 4B parameters per token. Attention is DeepSeek-style MLA with a compressed cache of about 46 KB per token, so context is cheap next to the weights: at Q4_K_M a 32K window adds only 1.4 GB. At Q4_K_M it needs about 21.2 GB at 4K, tight on a 24 GB card. IQ4_XS needs about 19.0 GB at 4K, comfortable on a 24 GB card. Q3_K_M needs about 17.0 GB at 4K, comfortable on a 20 GB card. Q2_K needs about 13.6 GB at 4K, comfortable on a 16 GB card. The full 262,144-token window at Q4_K_M needs about 33.3 GB at 256K. Each GGUF file also carries a 1.7B-parameter multi-token-prediction block that llama.cpp skips unless speculative decoding asks for it, so real use is about 1 GB under these figures at Q4_K_M. Sizes come from bartowski's GGUF files, and no per-level quality loss has been published.
262K
Max Context
9
Quant Variants
GGUF Q8_0
Best Quality
—
Perplexity rise (best build)
Quantization Variants
Per-quant VRAM, quality loss, and inference speed on RTX 4090
Measured = run on this site · Estimated = not run here: calculated, or a figure this site has not verified · Community = public reports
| Format | Level | BPW | VRAM | PPL Loss | Speed | Source | Actions |
|---|---|---|---|---|---|---|---|
| GGUF | Q8_0 | 8.51 | 34.9 GB | — | — | Estimated | |
| GGUF | Q6_K | 6.97 | 28.6 GB | — | — | Estimated | |
| GGUF | Q5_K_M | 6.15 | 25.3 GB | — | — | Estimated | |
| GGUF | Q4_K_M | 5.14 | 21.2 GB | — | — | Estimated | |
| GGUF | IQ4_XS | 4.61 | 19.0 GB | — | — | Estimated | |
| GGUF | Q3_K_M | 4.12 | 17.0 GB | — | — | Estimated | |
| GGUF | IQ3_XXS | 3.7 | 15.3 GB | — | — | Estimated | |
| GGUF | Q2_K | 3.29 | 13.6 GB | — | — | Estimated | |
| GGUF | IQ2_XXS | 2.64 | 11.0 GB | — | — | Estimated |
Which file each size is for
A file size is not a memory figure: the VRAM column is the calculator's total at 4K context — weights plus KV cache plus a 10% activation buffer. Units differ on purpose: file sizes are decimal GB, as Hugging Face lists them; the VRAM column is GiB (1024³ bytes) with 2% added to the weights, so 7.12 GB of file counts as about 6.8 GiB there. A vision projector (mmproj), where the repo ships one, is a separate download and is in neither number.
- GGUF Q8_0bartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-Q8_0.gguf · 33.22 GB (33,222,310,848 bytes) · listing read 2026-11-10
- GGUF Q6_Kbartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-Q6_K.gguf · 27.19 GB (27,191,114,688 bytes) · listing read 2026-11-10
- GGUF Q5_K_Mbartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-Q5_K_M.gguf · 24.00 GB (24,000,035,776 bytes) · listing read 2026-11-10
- GGUF Q4_K_Mbartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-Q4_K_M.gguf · 20.06 GB (20,056,603,584 bytes) · listing read 2026-11-10
- GGUF IQ4_XSbartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-IQ4_XS.gguf · 17.98 GB (17,982,561,216 bytes) · listing read 2026-11-10
- GGUF Q3_K_Mbartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-Q3_K_M.gguf · 16.10 GB (16,100,834,240 bytes) · listing read 2026-11-10
- GGUF IQ3_XXSbartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-IQ3_XXS.gguf · 14.43 GB (14,433,573,824 bytes) · listing read 2026-11-10
- GGUF Q2_Kbartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-Q2_K.gguf · 12.84 GB (12,841,507,776 bytes) · listing read 2026-11-10
- GGUF IQ2_XXSbartowski/XingChen-AGI_Xing4.0-29B-A4B-GGUF · XingChen-AGI_Xing4.0-29B-A4B-IQ2_XXS.gguf · 10.32 GB (10,317,247,424 bytes) · listing read 2026-11-10
Similar models
Compare with GPT-OSS 20BGPT-OSS 20B
OpenAI GPT-OSS
OpenAI open-weight MoE (21B total / 3.6B active), shipped natively in MXFP4 — ~12.8GB runs on a 16GB card with no quality tax. Only 3.6B active params means CPU-offload stays usable.
Qwen3 30B-A3B Instruct
Alibaba Qwen3
Qwen3 MoE with only 3B active params. Q4 ~19GB file; outperforms QwQ-32B on 16GB cards.
Qwen3-VL 30B-A3B Instruct
Alibaba Qwen3-VL
Multimodal MoE with only ~3B active parameters, so it stays responsive on Apple unified memory and survives CPU offload far better than a dense 30B. At Q4_K_M it needs about 19.9 GB at 4K, comfortable on a 24 GB card; Q3_K_M brings that to 15.1 GB. The vision encoder is a separate 1.1 GB file.
Magistral Small 1.2 24B
Mistral Magistral
Mistral's reasoning model on a Mistral Small 3.2 base, with reasoning wrapped in [THINK] tags. At Q4_K_M it needs about 15.7 GB at 4K, tight on a 16 GB card and comfortable on 20 GB — explicit chain-of-thought a level below the 70B-class reasoners most guides assume.
Running Xing4.0 29B-A4B locally
At Q4_K_M and 4K of context, Xing4.0 29B-A4B needs about 21.2 GB — 19.1 GB of weights, 0.18 GB of KV cache and a 1.9 GB activation buffer. The smallest cards in this index that clear that comfortably are 32 GB ones — 4 of them, from the RTX 5090 up — and 26 of the 78 cards here do. These are calculated figures, not measurements: the estimate stops counting a card as comfortable at 88% of its VRAM, which is roughly the room a desktop session needs.
What longer context costs
Going from 4K to 32K adds about 1.23 GB, taking the total to 22.5 GB. Weights do not move with context — only the KV cache does, and it grows linearly, so this is the number to watch when planning for long documents. The model's native window is 256K; holding all of it at Q4_K_M would need about 33 GB.
Which build to download
This index only tracks Xing4.0 29B-A4B in GGUF, across 9 levels (Q8_0, Q6_K, Q5_K_M, Q4_K_M, IQ4_XS, Q3_K_M, IQ3_XXS, Q2_K, IQ2_XXS). No per-level perplexity sweep has been published for this model, so the quality column is empty rather than estimated — within one model, more bits per weight is the only ordering the data supports. No throughput has been measured for this model on this site's hardware. GGUF runs on llama.cpp and Ollama across NVIDIA, AMD and Apple silicon; AWQ and GPTQ target vLLM on CUDA and ROCm; EXL2 is ExLlamaV2 — CUDA only, and now archived, so local use rather than serving.
Common questions
- How much VRAM does Xing4.0 29B-A4B need?
- About 21.2 GB at Q4_K_M with 4K of context and batch 1, rising to roughly 22.5 GB at 32K. That figure is weights plus KV cache plus a 10% activation buffer, calculated from the model's architecture rather than measured on a card.
- Will Xing4.0 29B-A4B run on a 32GB GPU?
- Yes — at Q4_K_M and 4K context it needs about 21.2 GB, which leaves 10.8 GB spare on a RTX 5090, or on any of the other 32 GB cards here (4 in all). That is the smallest size in this index that clears it comfortably; 26 of 78 do.
- Which quantization of Xing4.0 29B-A4B should I use?
- No published quality comparison exists for this model, so pick by footprint: Q4_K_M is the level most people run, and a higher bits-per-weight level is more faithful. All 9 levels in the index are Q8_0, Q6_K, Q5_K_M, Q4_K_M, IQ4_XS, Q3_K_M, IQ3_XXS, Q2_K, IQ2_XXS. Note this is a mixture-of-experts model — all parameters must be resident even though only a fraction are active per token, so the memory cost follows the total, not the active count.
Where this model fits
Sized at Q4_K_M with a 4K context window, smallest card first. Comfortable means the estimate uses at most 88% of the memory.
- Runs comfortably on
- RTX 509032GB · +10.8Arc Pro B70 32G32GB · +10.8Radeon AI PRO R9700 32G32GB · +10.8Instinct MI100 32G32GB · +10.8Mac M3 Pro 36G36GB · +5.8
- Tight but possible
- RTX 309024GBRadeon RX 7900 XTX24GBRTX 409024GB
- Ships in
- GGUF
- A top pick for
- Best local LLM for 16GB
- Try it yourself
- Size it in the calculatorGenerate the run command
How to actually run this
Deployment guides for this model and this class of hardware.
This page's figures change when the model or the runtime does.Last updated 2026-11-11 RSS → /feed.xml