Photo by Lee Campbell on Unsplash. Source: https://unsplash.com/photos/person-facing-monitor-while-typing-during-daytime-6njoEbtarec (Unsplash License).

A hyperscaler just published the number that decides whether a gigawatt cluster is worth what it cost. It is not the GPU count.

  • Meta converted a data center that had served web traffic two years ago into training infrastructure, and the first completed phase ran above 85 percent goodput on pre-training and above 90 percent on reinforcement learning.
  • A two rack pair draws about 120 kilowatts and forms one 72 GPU NVLink domain, so a single degraded host or switch can stall an entire job.
  • Getting from about 47,000 to more than 54,000 GPU hours between interruptions took memory scrubbing, tighter HBM firmware, a better LPDDR error correction algorithm and predictive retirement of devices before a job found them.
  • The stated target is two interruptions per 8,000 GPUs per day, and the next platform draws more again with Vera Rubin above 170 kilowatts per rack.
  • Almost none of that appears on a quote, which is the part most infrastructure plans still miss.

Read the full analysis at Why 85 percent goodput is the number that decides a gigawatt cluster.

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.