Urgent.News

One page, thousands of outlets. See who else covered it.

Editions

AI

AMD inches closer to its goal of making AI suck less ... energy

House of Zen claims latest systems already 4x more efficient than two years ago

AMD inches closer to its goal of making AI suck less ... energy

AMD is making significant strides in improving the efficiency of its AI systems, aiming for a 20x boost in rack efficiency by the end of the decade. As of 2026, their systems are already 4x more efficient than they were in 2024. This progress has been driven by various optimizations, including support for 4-bit floating point data types, new memory technologies, faster interconnect speeds, and the transition from conventional GPU servers to fully-integrated rack-scale systems.

AMD's latest development is the Helios rack-scale compute platform, which houses 72 MI455X GPUs in a single massive system. While each MI455X GPU delivers up to 15.4x higher floating point performance and 4x faster memory compared to the MI300X, it also consumes more than 3x the power. However, AMD's success lies in its ability to scale AI workloads efficiently across the 72 accelerators.

Although Nvidia has launched similar rack-scale systems, AMD uses a different methodology for calculating efficiency, focusing on weighted max achieved FLOPS, memory, and interconnect bandwidth for training and inference. The first Helios units will be available this quarter, with MLPerf and InferenceX benchmarks to follow. If AMD meets its targets, two Helios racks could deliver the same computational power as 570 racks from 2024, effectively providing 20x more compute capacity with the same power consumption.

Written by urgent.news from The Register's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at theregister.com →

More in AI

From Flat Logs to Execution Trees: Debugging Modern AI Agents

An agent trace is usually written as a sequence of events because append-only data is simple to produce: span_started span_started span_ended span_started span_ended span_ended Developers do not want…

  • Agent traces appear as a series of events due to append-only data structure simplicity.
  • Developers construct execution trees to visualize relationships between operations.
  • Reliable execution tree requires stable trace and span identity assignment.

Stripe didn’t really buy OpenRouter because of the ‘singularity’

What does a payments giant want with a startup that routes prompts between different AI models? Stripe says it's because of "the singularity" but it's really for a far more real and powerful reason.

  • Stripe acquired OpenRouter for $7.5 billion.
  • Acquisition driven by AI's economic impact, not singularity.
  • OpenRouter's founders receive $1.5 billion, more than company's valuation.

More from Wednesday 19 August →