Density Arrives on a Roadmap

"The pool grows when a die does. The die grows on the memory vendors' calendar, which Apple reads like everyone else and cannot advance."

Where 512 Comes From

Sixteen channels, sixteen memory packages — the wire lesson's inference — and 32 GB in each package makes 512. Thirty-two gigabytes in a package is what LPDDR5X could stack in 2025: Micron describes its 128 GB module as "four placements of 16-die stacks", which is 32 GB a stack from 16-gigabit dies sixteen high; Samsung in 2024 put "single package capacity of mobile DRAM up to 32-gigabytes". So the Studio's 512 is not a number Apple chose from a menu; it is the largest LPDDR package that existed, times the number of packages the bus could reach. The M5 Ultra ships the same 512 a year and a half later with a faster bus, because the package did not grow in the interval.

Where 1 TB Comes From

The code block does the multiplication for the next die. In March 2026 Micron announced the "industry's first monolithic 32Gb LPDDR5X die" in a 256 GB server module; a 32-gigabit die sixteen high is 64 GB a package, and sixteen packages are 1 TB on the same sixteen channels at the same bandwidth per channel — a terabyte at the M5 Ultra's 1.2 TB/s, which is 1.2 GB/s per gigabyte, the pool's law again. Beyond that, JEDEC's LPDDR6 roadmap describes a wider 24-bit sub-channel that "allows more die per package and higher memory capacities per component and per channel" with "512GB density on the horizon" per component; at that density the same sixteen packages would hold several terabytes, at LPDDR6's 10.7-gigabit-and-up pin rates. None of those dates are Apple's. They are Micron's, Samsung's, SK hynix's and the standards body's, and a Mac's ceiling follows them by however long it takes to qualify a package on a bus that has no length to spare.

The Household's Reading

The homework this lesson sets Apple is small: be first to the denser die, on a bus already wide enough to make it count. That is not a design problem; it is a procurement and qualification problem in a market where, the first lesson noted, the vendors' capacity has shifted toward the high-margin memory the rivals' racks buy. The household's position from its doctrine reads the same calendar from the buyer's side: the pool's ceiling rises when the die does, the die arrives on a roadmap, and the used prior generation is the honest price gauge until then — two 512 GB Studios of the previous generation hold more than one of the new at half the price per gigabyte, with the single-stream decode ceiling the only axis the new machine wins. Waiting with a term, the doctrine calls it; the term is the memory vendors' 2026–2027 die schedule, which is public, and the next track is about the waiting.

Code

density.py — dies per package, packages per bus, and the terabyte on the next die·python

#!/usr/bin/env python3
"""Density arrives on a roadmap. A pool's capacity is packages x dies per package x bits
per die. Vendor die and stack figures; the package count on a Mac is this quest's inference
from the channel fit (16 channels on an Ultra), not an Apple statement."""
packages = 16                                        # one LPDDR package per 64-bit channel, inferred
for label, gbit_per_die, dies in [("LPDDR5X 16Gb dies, 16-high (Micron's 128 GB module uses four such stacks)", 16, 16),
                                  ("LPDDR5X 32Gb monolithic die, 16-high (Micron, 2026-03)", 32, 16),
                                  ("LPDDR6 roadmap: '512GB density on the horizon' per component (JEDEC reprint, 2026-05)", None, None)]:
    if gbit_per_die:
        per_pkg = gbit_per_die * dies / 8
        print(f"{label}\n    {per_pkg:.0f} GB per package x {packages} = {per_pkg*packages:.0f} GB on an Ultra-class bus")
    else:
        print(f"{label}\n    a per-component density that would put multiple terabytes on the same 16 packages")
print("\nthe 512 GB Studio is 32 GB per package x 16 (inferred); 1 TB on the same bus is the next die or the next stack height, on the memory vendors' calendar, not Apple's.")

Exercise

Find the current largest LPDDR package a memory vendor sells and the die it is built from. Multiply by the channel count you inferred for your Mac's tier in the wire lesson and write the result on your card as your tier's next ceiling — with the vendor's ship date beside it.

Hint

The vendor's date is for modules or samples; the Mac follows by the time it takes to qualify. If the number you get is the ceiling your Mac already has, the die has not moved yet and the next one is the one to watch.