DeepReinforce, United States · Released August 18, 2026
Ornith 1.5 35B-A3B has 36.0B parameters (3B active per token). In BF16 its weights alone take 65.4 GiB; quantized to 4-bit, about 19.6 GiB. Each 32K-token request adds 0.63 GiB of KV cache. Cheapest way to run it today: 1 × GeForce RTX 3090 (24 GB) at $0.143 per hour.
Read every day from Hugging Face. Split files are added together; vision projectors are left out.
How many GPUs to run Ornith 1.5 35B-A3B
Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.
GPU
BF16 / FP16
FP8 / INT8
4-bit (GGUF Q4_K_M)
GeForce RTX 4090 24 GB
4
2
1
GeForce RTX 5090 32 GB
3
2
1
RTX PRO 6000 Blackwell 96 GB
1
1
1
Mac M5 Max 128 GB 96 GB usable
1
1
1
NVIDIA H100 80 GB
1
1
1
NVIDIA H200 141 GB
1
1
1
NVIDIA B200 (HGX) 180 GB
1
1
1
Cheapest way to run Ornith 1.5 35B-A3B today
For each GPU: the fewest cards that fit Ornith 1.5 35B-A3B with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-10-10).
On-demand prices from RunPod, Vast.ai, Verda and Azure, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.
KV cache: how memory grows with context
Architecture: 40 layers · 10 full attention (2 KV × 256) · 30 linear attention. Its KV cache is 4.0× smaller than if every layer used full attention, because only 10 of its 40 layers keep a KV cache; the others hold a small fixed-size state. Only 3B parameters are active per token, but all 36B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.16 GiB
0.08 GiB
32K tokens
0.63 GiB
0.31 GiB
128K tokens
2.50 GiB
1.25 GiB
256K tokens
5.00 GiB
2.50 GiB
Plus 61.4 MiB of recurrent state per request, whatever the context.
Ornith 1.5 35B-A3B VRAM FAQ
How much VRAM does Ornith 1.5 35B-A3B need?
In BF16 the weights alone take 65.4 GiB (70 GB). In FP8 that is 33.6 GiB, and about 19.6 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 0.16 GiB at 8K tokens and 0.63 GiB at 32K (BF16 cache).
Can Ornith 1.5 35B-A3B run on a single RTX 4090 (24 GB)?
Yes. In 4-bit (GGUF Q4_K_M) it fits on one RTX 4090 with an 8K-token context (19.8 GiB including the cache, with llama.cpp).
What is the cheapest way to run Ornith 1.5 35B-A3B?
On 2026-10-10, the cheapest on-demand setup is 1 × GeForce RTX 3090 (24 GB) with 4-bit (GGUF Q4_K_M) weights on Vast.ai, at $0.143 per hour (about $104.39 per month). Next: 1 × GeForce RTX 4090 (24 GB) with 4-bit (GGUF Q4_K_M) weights on Vast.ai, at $0.348 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Ornith 1.5 35B-A3B need?
With one request and an 8K-token context: 1 in BF16, 1 in FP8 and 1 in 4-bit (vLLM, 90% of memory usable). Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
Ornith 1.5 35B-A3B VRAM badge
For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/ornith-1-5-35b-a3b.json.
Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.