DeepReinforce, United States · Released October 20, 2026New
Ornith-1.5 122B has 125.1B parameters (9B active per token). In BF16 its weights alone take 228 GiB; quantized to 4-bit, about 68.8 GiB. Each 32K-token request adds 0.75 GiB of KV cache. Cheapest way to run it today: 2 × RTX A6000 (48 GB) at $0.432 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 122B
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
8-bit
4-bit
GeForce RTX 4090 24 GB
16 (several machines)
6
4
GeForce RTX 5090 32 GB
8
4
3
RTX PRO 6000 Blackwell 96 GB
3
2
1
Mac M5 Max 128 GB 96 GB usable
3
2
1
Ryzen AI Max+ 395 128 GB 96 GB usable
3
2
1
DGX Spark (GB10) 128 GB
2
1
1
NVIDIA H100 80 GB
4
2
2
NVIDIA H200 141 GB
2
1
1
NVIDIA B200 (HGX) 180 GB
2
1
1
8-bit: FP8 with vLLM (INT8 on GPUs without FP8), Q8_0 with llama.cpp. 4-bit: AWQ / GPTQ with vLLM, Q4_K_M with llama.cpp, both counted at the Q4_K_M size.
Cheapest way to run Ornith-1.5 122B today
For each GPU: the fewest cards that fit Ornith-1.5 122B with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-10-20).
On-demand prices from AWS, Google Cloud, Azure, RunPod, Vast.ai, Oracle Cloud, OVHcloud, Scaleway, Verda, Akash and UpCloud, 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.
Architecture: 48 layers · 12 full attention (2 KV × 256) · 36 linear attention. Its KV cache is 4.0× smaller than if every layer used full attention, because only 12 of its 48 layers keep a KV cache; the others hold a small fixed-size state. Only 9B parameters are active per token, but all 125B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.19 GiB
0.09 GiB
32K tokens
0.75 GiB
0.38 GiB
128K tokens
3.00 GiB
1.50 GiB
256K tokens
6.00 GiB
3.00 GiB
Plus 147 MiB of recurrent state per request, whatever the context.
Ornith-1.5 122B VRAM FAQ
How much VRAM does Ornith-1.5 122B need?
In BF16 the weights alone take 228 GiB (245 GB). In FP8 that is 116 GiB, and about 68.8 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 0.19 GiB at 8K tokens and 0.75 GiB at 32K (BF16 cache).
Can Ornith-1.5 122B run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 4 RTX 4090s. In 4-bit it fits on a single RTX PRO 6000 Blackwell (96 GB).
Can Ornith-1.5 122B run on an RTX 5090 (32 GB)?
No. Even in 4-bit it needs 3 RTX 5090s.
Can Ornith-1.5 122B run on a Mac?
Yes. In 4-bit (Q4_K_M with llama.cpp) it needs a Mac with 96 GB of unified memory or more, of which macOS gives the GPU about 72 GB, for one request with an 8K-token context. In 8-bit (Q8_0) it needs 192 GB or more.
Can Ornith-1.5 122B run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
Yes. On a DGX Spark (128 GB) it fits in Q8_0 (116 GiB with an 8K-token context); on a Ryzen AI Max+ 395 with 128 GB, whose GPU gets up to 96 GB, it fits in Q4_K_M (69.1 GiB with an 8K-token context), with llama.cpp and one request.
What is the cheapest way to run Ornith-1.5 122B?
On 2026-10-20, the cheapest on-demand setup is 2 × RTX A6000 (48 GB) with Q4_K_M weights on Vast.ai, at $0.432 per hour (about $315.36 per month). Next: 4 × GeForce RTX 3090 (24 GB) with Q4_K_M weights on Vast.ai, at $0.484 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Ornith-1.5 122B need?
With one request and an 8K-token context: 4 in BF16, 2 in FP8 and 2 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 122B 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-122b.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.