Metis-1.6 Logos
10B MoEMetis
The larger of Lernex's two Metis-1.6 models, released on 1 November under Apache 2.0. It is a looped hybrid: 20 layers, mostly Mamba-2 with three attention layers and a mixture-of-experts block on every layer, and the whole stack runs twice per token, so each token reads about 2.6B parameters' worth of weights from a 10.24B model. Each pass keeps its own attention cache, about 15 KB per token in total. IQ4_XS needs about 6.4 GB at 4K and 6.9 GB at 32K, comfortable on an 8 GB card. Q4_K_M needs about 7.1 GB at 4K, tight on an 8 GB card and comfortable from 10 GB up; at 128K it needs about 9.1 GB, comfortable on a 12 GB card. Q8_0 needs about 11.7 GB at 4K, comfortable on a 16 GB card. llama.cpp runs it since 3 November. Sizes come from Lernex's own GGUF files, and no per-level quality loss has been published.
131K
Max Context
5
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 | IQ4_XS | 4.74 | 6.4 GB | — | — | Estimated | |
| GGUF | Q4_K_M | 5.27 | 7.1 GB | — | — | Estimated | |
| GGUF | Q5_K_M | 6.12 | 8.3 GB | — | — | Estimated | |
| GGUF | Q6_K | 6.91 | 9.3 GB | — | — | Estimated | |
| GGUF | Q8_0 | 8.68 | 11.7 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 IQ4_XSLernex/Metis-1.6-Logos-GGUF · Metis-1.6-Logos-IQ4_XS.gguf · 6.07 GB (6,065,003,936 bytes) · listing read 2026-11-04
- GGUF Q4_K_MLernex/Metis-1.6-Logos-GGUF · Metis-1.6-Logos-Q4_K_M.gguf · 6.74 GB (6,744,975,776 bytes) · listing read 2026-11-04
- GGUF Q5_K_MLernex/Metis-1.6-Logos-GGUF · Metis-1.6-Logos-Q5_K_M.gguf · 7.83 GB (7,834,279,776 bytes) · listing read 2026-11-04
- GGUF Q6_KLernex/Metis-1.6-Logos-GGUF · Metis-1.6-Logos-Q6_K.gguf · 8.85 GB (8,847,425,376 bytes) · listing read 2026-11-04
- GGUF Q8_0Lernex/Metis-1.6-Logos-GGUF · Metis-1.6-Logos-Q8_0.gguf · 11.11 GB (11,105,534,816 bytes) · listing read 2026-11-04
Similar models
Compare with Metis-1.6 PraxisMetis-1.6 Praxis
Metis
The smaller of Lernex's two Metis-1.6 models, released on 1 November under Apache 2.0. It is a looped hybrid: 12 layers, mostly Mamba-2 with two attention layers and a small mixture-of-experts block on every layer, and the whole stack runs twice per token, so each token reads about 1.1B parameters' worth of weights from a 2.95B model. Each pass keeps its own attention cache, about 8 KB per token in total, which makes its 128K window cheap. At Q4_K_M it needs about 2.2 GB at 4K and 3.2 GB at 128K, comfortable on a 4 GB card. Q8_0 needs about 4.5 GB at 128K, comfortable on a 6 GB card. llama.cpp runs it since 3 November. Sizes come from Lernex's own GGUF files, and no per-level quality loss has been published.
Qwen3-VL 8B Instruct
Alibaba Qwen3-VL
Current-generation vision-language model that still fits a single 8–12GB card at Q4 (~5.9GB). The realistic multimodal option for people without a 24GB GPU — note the vision encoder adds VRAM the KV-cache math below does not model.
Qwen3.5 9B
Alibaba Qwen3.5
The newest small Qwen and a common pick for 8 to 16 GB cards. Only 8 of its 32 layers keep a growing KV cache, so it can use a long context on modest hardware. At Q4_K_M it needs about 6.6 GB at 4K and 7.0 GB at 16K, comfortable on an 8 GB card; at 32K (7.5 GB) it is tight there and comfortable from 10 GB up. Its full 256K window needs about 15.2 GB. Q8_0 needs about 10.4 GB, comfortable from 12 GB up. Reasoning is off by default on the small Qwen3.5 sizes, and it reads images through a separate vision encoder. Sizes come from the published GGUF file sizes, and no per-level quality loss has been published.
Granite 4.2 8B
IBM Granite
IBM's dense 8B reasoning model from the Granite 4.2 family (3B, 8B, 30B), released in August under Apache 2.0. Thinking is on by default; a non-thinking and a low-effort mode are chosen through the chat template. Unlike Granite 4.0's hybrid models it is a plain transformer, so llama.cpp runs it as `granite` and every one of its 40 layers keeps a full cache: about 6.5 GB at Q4_K_M with a 4K context, 11.3 GB at 32K and 27.8 GB across the whole 128K window. That makes it an 8 GB card model at short contexts and a 16 GB one for long documents. Sizes come from bartowski's GGUF files; IBM publishes no perplexity by quantization level, so no quality-loss figure is shown.
Running Metis-1.6 Logos locally
At Q4_K_M and 4K of context, Metis-1.6 Logos needs about 7.1 GB — 6.4 GB of weights, 0.06 GB of KV cache and a 0.7 GB activation buffer. The smallest cards in this index that clear that comfortably are 10 GB ones — 2 of them, from the Arc B570 10G up — and 67 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 0.41 GB, taking the total to 7.6 GB. That is gentler than the parameter count suggests: only 6 of 20 layers keep a KV cache that grows with context, so the cache scales at a fraction of the usual rate. The model's native window is 128K; holding all of it at Q4_K_M would need about 9 GB.
Which build to download
This index only tracks Metis-1.6 Logos in GGUF, across 5 levels (IQ4_XS, Q4_K_M, Q5_K_M, Q6_K, Q8_0). 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 Metis-1.6 Logos need?
- About 7.1 GB at Q4_K_M with 4K of context and batch 1, rising to roughly 7.6 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 Metis-1.6 Logos run on a 10GB GPU?
- Yes — at Q4_K_M and 4K context it needs about 7.1 GB, which leaves 2.9 GB spare on a Arc B570 10G, or on any of the other 10 GB cards here (2 in all). That is the smallest size in this index that clears it comfortably; 67 of 78 do.
- Which quantization of Metis-1.6 Logos 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 5 levels in the index are IQ4_XS, Q4_K_M, Q5_K_M, Q6_K, Q8_0. 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
- Arc B570 10G10GB · +2.9RTX 3080 10G10GB · +2.9RTX 3060 12G12GB · +4.9Radeon RX 6700 XT12GB · +4.9Radeon RX 7700 XT12GB · +4.9
- Tight but possible
- RTX 40608GBRTX 4060 Ti 8G8GBRadeon RX 9060 XT 8G8GB
- Just misses
- Mac M1 8G+1.1GB overMac M3 8G+1.1GB over
- Ships in
- GGUF
- 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-05 RSS → /feed.xml