text model · Ornith · Linux
Can I run Ornith 1.0 35B on Nvidia DGX Spark (128GB)?
Yes. Ornith 1.0 35B runs on Nvidia DGX Spark (128GB) at Q4_K_M (~23.2 GB of ~112 GB usable).
Runs at Q4_K_M using ~23.2 GB of ~112 GB usable. You have room for FP16 for higher quality.
That figure is at a 4k context and moves about ±15% as context length changes. Nvidia DGX Spark (128GB) leaves ~88.8 GB of headroom, room to step up to FP16 for higher quality.
- Q4_K_M needed
- ~23.2 GB
- Usable on device
- ~112 GB
- Device memory
- 128 GB
- Best quant
- Q4_K_M
Which quant fits
Run it
Pick your tool. All 3 load the same Q4_K_M weights.
ollama run ornith:35b llama-cli -hf deepreinforce-ai/Ornith-1.0-35B-GGUF:Q4_K_M lms get deepreinforce-ai/Ornith-1.0-35B-GGUF - Parameters
- 35B (MoE, 3B active)
- Q4_K_M size
- 21 GB
- Q8_0 size
- 37 GB
- Context
- 256k
- Ollama tag
- ornith:35b
- Memory
- 128 GB unified
- Usable for weights
- ~112 GB
- Power draw
- ~140 W
- Best runtime
- llama.cpp (CUDA) / Ollama (CUDA)
You could also run
Run Ornith 1.0 35B on other hardware
FAQ
Can Nvidia DGX Spark (128GB) run Ornith 1.0 35B?
Yes. Ornith 1.0 35B runs on Nvidia DGX Spark (128GB) at Q4_K_M (~23.2 GB of ~112 GB usable).
How much memory does Ornith 1.0 35B need?
Nvidia DGX Spark (128GB) has room to spare. At Q4_K_M the weights are ~21 GB; with KV cache and runtime overhead, budget ~23.2 GB at a 4k context. It is a Mixture-of-Experts model (35B total / 3B active), so all experts must stay in memory; memory tracks total params, not active params.
What is the best tool to run Ornith 1.0 35B on Linux?
Ollama for a simple setup; vLLM for the most speed. vLLM shines for multi-user serving/throughput. For a single local chat, Ollama or llama.cpp is simpler and lighter.
Embed this
[](https://localmodel.run/can-i-run/ornith-1.0-35b/nvidia-dgx-spark-128gb) Sources
-
deep-reinforce.com · 1 source
-
docs.nvidia.com · 2 sources
-
github.com · 1 source
-
huggingface.co · 2 sources
-
nvidia.com · 1 source
-
nvidianews.nvidia.com · 1 source
-
ollama.com · 2 sources
-
tomshardware.com · 1 source
Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.