Photo by Lyubomyr Reverchuk on Unsplash. Source: https://unsplash.com/photos/a-man-and-a-woman-sitting-at-a-table-with-a-laptop-CvyRP10doo0 (Unsplash License).

Reflection published the weights for a 501 billion parameter model on Friday under Apache 2.0. The parameter count is the headline. The memory arithmetic is the story.

  • NVFP4 cuts the checkpoint from about 1 TB to roughly 280 GB, which fits on four B300 GPUs.
  • Hybrid attention holds the cache at 36 KiB per token, so a single 1M context reserves 36.08 GiB.
  • On that four GPU node roughly 19 full length contexts fit at once, against about 3 if every layer kept full history.
  • 23 billion parameters are active per token, so compute behaves like a much smaller model while memory behaves like a 501B one.

Day one support landed in Transformers, vLLM, SGLang, Unsloth and NVIDIA Dynamo, with a DFlash2 speculative drafter alongside. The checkpoint arrives with a serving path rather than a research notebook.

We ran the capacity math on the published figures. Full analysis here.

By Ivan Tarin

Ivan Tarin is a Principal Product Marketing Manager at SUSE, where he owns go-to-market strategy and positioning for a seven-product cloud-native portfolio spanning Kubernetes, virtualization, storage, security, and observability. A former full-stack developer who shipped production code for enterprise and public-sector clients including U.S. national laboratories, Ivan translates complex infrastructure and AI technology into messaging that lands with developers, platform teams, and enterprise buyers. He has presented at KubeCon, SUSECON, and AWS Developer Week, and is currently pursuing an MS in Artificial Intelligence at the University of Colorado Boulder.

Leave a Reply

Your email address will not be published. Required fields are marked *

Get the next one before it is old news

Independent analysis of cloud-native infrastructure, Kubernetes and data center economics. No vendor spin.