Ornith-1.0-35B GGUF size and VRAM requirements

License: mit ⬇ 46,707 ❤ 152
Context262,144

unsloth/Ornith-1.0-35B-GGUF is a language model, built on the qwen35moe architecture. It is released under the mit license and has been downloaded 46,707 times.

Ornith-1.0-35B-GGUF is a Mixture-of-Experts model with 256 experts, of which 8 are active on each token. Routing only 8 of 256 experts makes it noticeably faster than a dense model of the same size — but every expert still has to be held in memory, so the numbers below are set by the full parameter count, not the active one. It is built from 40 transformer layers, a hidden size of 2,048, 16 attention heads. It uses a hybrid attention design: only 10 of its 40 layers keep a full KV cache, while the rest use linear attention with a constant-size state. Long contexts therefore cost far less memory than on a conventional model of this size.

To run unsloth/Ornith-1.0-35B-GGUF locally at a 4,096-token context, its quantized versions need between 10.68 GB (IQ1_S, lowest quality) and 65.49 GB (BF16, highest quality) of memory, weights plus KV cache and a system margin included. Context length drives that memory directly: at 4,096 tokens the KV cache for Ornith-1.0-35B-GGUF is about 0.08 GB, rising to roughly 5.0 GB at its full 262,144-token context. Shorter prompts free up memory for a higher-quality quantization.

For most users the best balance is Q4_K_XL, needing about 21.67 GB. That means unsloth/Ornith-1.0-35B-GGUF fits entirely in the VRAM of a 12 GB GPU or larger, running fully on the GPU.

Available GGUF quantizations for unsloth/Ornith-1.0-35B-GGUF include IQ1_S, IQ1_M, IQ2_XXS, IQ2_M, Q2_K_XL, IQ3_XXS, IQ3_S, Q3_K_M, Q3_K_XL, IQ4_XS, IQ4_NL, Q4_K_S, MXFP4, Q4_K_M, Q4_K_XL, Q5_K_S, Q5_K_M, Q5_K_XL, Q6_K, Q6_K_XL, Q8_0, Q8_K_XL, BF16. The model supports a native context length of up to 262,144 tokens; a longer context grows the KV cache and the memory needed.

→ Guide: How much VRAM do you need?

GGUF file size and memory by quantization

Compare real GGUF weight sizes, estimated KV cache and total memory for Q4, Q5, Q8 and every quantization published in this repository.

Quant.Bits QualityWeights KVTotal Speed~Verdict
IQ1_S 126612.3 Excellent 9.8 GB 0.08 GB 10.68 GB 5.1 t/s Offload
IQ1_M 132869.59 Excellent 10.29 GB 0.08 GB 11.16 GB 4.9 t/s Offload
IQ2_XXS 138319.49 Excellent 10.71 GB 0.08 GB 11.59 GB 4.7 t/s Offload
IQ2_M 139120.58 Excellent 10.77 GB 0.08 GB 11.65 GB 4.6 t/s Offload
Q2_K_XL 147396.35 Excellent 11.41 GB 0.08 GB 12.29 GB 4.4 t/s Offload
IQ3_XXS 165340.93 Excellent 12.8 GB 0.08 GB 13.68 GB 3.9 t/s Offload
IQ3_S 180277.69 Excellent 13.96 GB 0.08 GB 14.83 GB 3.6 t/s Offload
Q3_K_M 200683.38 Excellent 15.53 GB 0.08 GB 16.41 GB 3.2 t/s Offload
Q3_K_XL 202165.21 Excellent 15.65 GB 0.08 GB 16.53 GB 3.2 t/s Offload
IQ4_XS 213973.33 Excellent 16.56 GB 0.08 GB 17.44 GB 3.0 t/s Offload
IQ4_NL 217909.37 Excellent 16.87 GB 0.08 GB 17.75 GB 3.0 t/s Offload
Q4_K_S 251365.7 Excellent 19.46 GB 0.08 GB 20.34 GB 2.6 t/s Offload
MXFP4 260719.61 Excellent 20.18 GB 0.08 GB 21.06 GB 2.5 t/s Offload
Q4_K_M 266302.47 Excellent 20.61 GB 0.08 GB 21.49 GB 2.4 t/s Offload
Q4_K_XL 268591.69 Excellent 20.79 GB 0.08 GB 21.67 GB 2.4 t/s Offload
Q5_K_S 300080.0 Excellent 23.23 GB 0.08 GB 24.11 GB Insufficient
Q5_K_M 318296.8 Excellent 24.64 GB 0.08 GB 25.52 GB Insufficient
Q5_K_XL 319154.65 Excellent 24.71 GB 0.08 GB 25.58 GB Insufficient
Q6_K 352610.99 Excellent 27.3 GB 0.08 GB 28.17 GB Insufficient
Q6_K_XL 383115.29 Excellent 29.66 GB 0.08 GB 30.53 GB Insufficient
Q8_0 443984.93 Excellent 34.37 GB 0.08 GB 35.25 GB Insufficient
Q8_K_XL 459605.5 Excellent 35.58 GB 0.08 GB 36.46 GB Insufficient
BF16 834676.46 Excellent 64.61 GB 0.08 GB 65.49 GB Insufficient

KV cache computed from the model's exact architecture. Speed is a rough estimate bounded by memory bandwidth.

Frequently asked questions

What kind of model is unsloth/Ornith-1.0-35B-GGUF?

unsloth/Ornith-1.0-35B-GGUF is a language model, based on the qwen35moe architecture. It is released under the mit license and distributed as GGUF files for local inference.

Is unsloth/Ornith-1.0-35B-GGUF a Mixture-of-Experts (MoE) model?

Yes. unsloth/Ornith-1.0-35B-GGUF is a Mixture-of-Experts model with 256 experts, of which 8 are activated per token. That makes it faster than a dense model of the same size, but all 256 experts must be loaded into memory, so the VRAM/RAM it needs is driven by the total parameter count, not the active one.

How does unsloth/Ornith-1.0-35B-GGUF handle long context?

unsloth/Ornith-1.0-35B-GGUF uses a hybrid attention design: only 10 of its 40 layers keep a full KV cache, and the rest use linear attention with a constant-size state. Long contexts cost far less memory than on a conventional model of this size.

How much VRAM do you need to run unsloth/Ornith-1.0-35B-GGUF?

You need about 11.65 GB of VRAM to run unsloth/Ornith-1.0-35B-GGUF entirely on the GPU using the IQ2_M quantization (at a 4,096-token context). Smaller quantizations lower the requirement at the cost of quality.

Can I run unsloth/Ornith-1.0-35B-GGUF on an 8 GB GPU?

Partially. unsloth/Ornith-1.0-35B-GGUF only fits on an 8 GB GPU by offloading part of it to system RAM (with Q4_K_XL), which runs but is slower.

Can I run unsloth/Ornith-1.0-35B-GGUF on a 16 GB GPU?

Yes. With 16 GB of VRAM you can run unsloth/Ornith-1.0-35B-GGUF fully on the GPU using IQ3_S (about 14.83 GB).

Can I run unsloth/Ornith-1.0-35B-GGUF on a 24 GB GPU?

Yes. With 24 GB of VRAM you can run unsloth/Ornith-1.0-35B-GGUF fully on the GPU using Q4_K_XL (about 21.67 GB).

What context length does unsloth/Ornith-1.0-35B-GGUF support?

unsloth/Ornith-1.0-35B-GGUF supports a native context length of up to 262,144 tokens. A longer context grows the KV cache, so it increases the memory needed to run the model.

What is the best quantization for unsloth/Ornith-1.0-35B-GGUF?

For unsloth/Ornith-1.0-35B-GGUF, a strong default is Q4_K_M, which needs about 21.49 GB and keeps most of the quality while roughly halving the memory versus 8-bit. With VRAM to spare, Q5_K_M or Q6_K add a little more quality; if you are tight on memory, a smaller quantization still runs. Pick the highest quantization that fits your VRAM.