The Memory Wall

Cross-cuts: Memory
· +2 sources in last 30d
Assessment draft · unreviewed
Viability
5/5
Drivers
4/5
Novelty
2/5
Diffusion
3/5
Impact
4/5

Timing Now (0-2yr) · Read Fairly rated

Von Neumann Bottleneck Von Neumann Bottlen… HBM (High-Bandwidth Memory) HBM (High-Bandwidth… HBM / CoWoS Bottleneck HBM / CoWoS Bottlen… Prefill vs Decode (LLM inference phases) Prefill vs Decode (… Processing-in-Memory (PIM) Processing-in-Memor… In-Memory Computing In-Memory Computing The Memor…

The memory wall is the widening gap between how fast processors can compute and how fast memory can feed them: peak hardware compute grew roughly 60,000x over two decades while DRAM bandwidth grew about 100x, which is why modern AI inference is limited by bytes moved rather than arithmetic 2024 Gholami Ai And Memory Wall.

Summary

What it is. “The memory wall” names a structural imbalance in computer architecture: arithmetic throughput has compounded far faster than the bandwidth and capacity of the memory that supplies operands to it. The canonical quantification comes from Gholami et al. (blog 2021, Hot Chips 2023, IEEE Micro 2024): over twenty years peak hardware compute rose ~60,000x, DRAM bandwidth ~100x, and interconnect bandwidth ~30x. Underneath those totals, peak server FLOPS scale at ~3.0x every two years, DRAM bandwidth at ~1.6x and interconnect bandwidth at ~1.4x 2024 Gholami Ai And Memory Wall. Because the rates differ, the share of workloads that are memory-bound rather than compute-bound grows monotonically with each hardware generation, regardless of any single design decision.

How it bites. Two mechanisms. First, throughput: if a kernel has low arithmetic intensity (few operations per byte fetched), the arithmetic units idle while weights arrive. In LLM serving the decode phase is the bandwidth-bound one, and one commentary describes GPU arithmetic units as spending most of their time stalled waiting for weights from HBM ref. Second, energy: an arithmetic operation costs sub-picojoule while an off-chip DRAM fetch costs roughly 1.3 to 2.6 nJ, so data movement, not computation, dominates the energy bill 2024 Gholami Ai And Memory Wall. Reasoning-style models make both worse, because long output sequences, low arithmetic intensity and tight latency budgets all push demand for bandwidth up and system utilisation down.

The parameters that decide it. For any given workload the wall is set by bytes fetched per useful operation (arithmetic intensity), by achievable bandwidth per package, by memory capacity per package (which decides how much of a model or KV cache stays local), and by the fraction of peak bandwidth a design can actually realise. That last parameter is where the commercial fight is: Positron’s second-generation Asimov silicon claims over 90% memory bandwidth utilisation on real transformer workloads against under 30% claimed for GPUs, using commodity LPDDR5x rather than HBM, at 864GB to 2.3TB capacity per chip and 2.76 TB/s realisable bandwidth ref. Groq attacks the same parameter from the other end, placing 230MB of on-die SRAM at 80 TB/s, roughly an order of magnitude above HBM bandwidth, at the cost of tiny capacity ref.

Evidence base

Open questions


Assessment drafted 2026-08-31 from up to 10 KB sources using the technology-scorecard framework; scores are a draft read pending review.

Recent mentions

Related concepts