Ornith 1.5 Beats 35B Models on Reasoning With Just 9B Parameters

Ornith-1.5-9B lands in NVFP4 format, delivering a Blackwell-native 4-bit reasoning model that punches near 35B-class agents at a fraction of the memory.

·
·
Ornith 1.5 Beats 35B Models on Reasoning With Just 9B ParametersPRO
  • Ornith-1.5-9B lands as an NVFP4-quantized dense reasoning model, MIT licensed and single-GPU friendly.
  • Built on Qwen3.5 and Gemma4 base with a self-improvement RL loop over tasks, scaffolds, and rollouts.
  • Hits 70.6 on SWE-bench Verified and 86.4 on GPQA Diamond, rivaling 35B MoE models.
  • NVFP4 cuts memory ~3.5x vs FP16 using Blackwell's native FP4 tensor cores.
  • 262K native context, extendable to ~1M tokens via YaRN RoPE scaling factor 4.0.
  • Serves through vLLM, SGLang, Ollama, llama.cpp with OpenAI-compatible tool calling.

Ornith 1.5 brings 9B reasoning to NVIDIA’s NVFP4

The Ornith model card has crossed 850,000 downloads on Hugging Face. The checkpoint combines a 9-billion-parameter dense reasoning model with NVIDIA’s NVFP4 format, targeting coding and agent workloads on a single Blackwell GPU. Hugging Face’s counter tracks file requests, so one user or automated job can generate multiple downloads.

A small model with an unusual training loop

According to the authors, Ornith 1.5 extends the training process used for Ornith 1.0, whose development drew on Qwen3.5 and Gemma 4 alongside continued pretraining, mid-training, and post-training. The new pipeline generates and selects tasks, adjusts the agent scaffolds that connect the model to tools, and improves the resulting solution rollouts through reinforcement learning.

  • Architecture: 9B dense model
  • Primary workloads: reasoning, coding, web research, and tool use
  • Native context: 262,144 tokens
  • Quantization: NVIDIA NVFP4
  • License: MIT
  • Other deployment target: a separate Ornith-1.5-9B-Mobile variant for mobile hardware

At BF16 precision, 9 billion parameters require about 18 GB for weights alone, with the release reporting a footprint near 19 GB. Runtime memory rises with the KV cache, batching, and framework overhead, especially near the advertised context limit. An 80 GB accelerator leaves substantial operating room, while smaller GPUs require tighter limits on context length and concurrency.

NVFP4 changes the memory math

NVFP4 stores weights as 4-bit floating-point values. Groups of 16 values share an FP8 scale, while an additional FP32 scale captures the tensor’s overall magnitude. This hierarchy preserves more range than a simple 4-bit integer representation while keeping the weight files compact.

Pro article

This story is for Pro members

You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.

Trending
  • No trending articles

Comments

avatar

Next Reads