Compute Economics & Frontier AI

The Token Explosion: Jevons Paradox, Moon Landings, and the Economics of Ambient Compute

In a world where lightweight distillation handles ninety percent of everyday digital tasks, humanity already produces multiple full-length libraries per person each day. Here is what six decades of computing history teach us about where those tokens will actually go.

Every era of modern technological expansion is defined by the sudden, violent collapse in the marginal cost of a single physical unit.

In the late eighteenth century, the unit was the foot-pound of mechanical work, unlocked when James Watt wrapped a separate condenser around Thomas Newcomen’s atmospheric engine. In the late nineteenth century, it was the lumen-hour of artificial illumination, created by ductile tungsten filaments and central electrical grids. In the twentieth century, it was the bit stored and the floating-point operation executed (FLOP), as photolithography etched planar silicon transistors down from millimeters to single-digit nanometers.

Today, the fundamental unit of civilizational output has shifted once again. We have crossed into the era of the token.

A token is not merely a collection of four ASCII characters or a sub-word embedding vector in a high-dimensional latent space. Economically and operationally, a token is the smallest discrete quantum of structured semantic reasoning. It is a unit of decision-making, syntax generation, visual comprehension, or symbolic deduction generated by an autoregressive neural network.

Over the past four years, public commentary has remained fixated on a singular anxiety: the physical, energetic, and financial scaling limits of trillion-parameter frontier models. We argue endlessly about 100-gigawatt nuclear power agreements, wafer-scale packaging yields, and synthetic data exhaustion.

Yet this fixation misses the far more profound revolution unfolding on the ground floor: the hyper-acceleration of inference efficiency.

Consider a simple, conservative thought experiment. Suppose the capabilities of foundation models reach a pragmatic architectural plateau for everyday applications. Suppose that a fast, distilled, lightweight architecture—a hypothetical DeepSeek V4 Flash, a high-throughput Mixture-of-Experts (MoE) with 3 billion active parameters per token, or a speculative multi-token decoding model—proves sufficiently capable of solving 90% of human digital tasks: writing code, summarizing documents, structuring database queries, and routing customer actions.

If the world’s currently deployed fleet of AI accelerators were dedicated purely to serving that class of model, how many tokens per day would humanity receive?

The first-principles arithmetic yields a number so vast that it breaks ordinary human intuition: over 400 trillion tokens every 24 hours. That is enough to allocate roughly 400,000 words per day to every knowledge worker on Earth—the equivalent of half of Leo Tolstoy’s War and Peace delivered to your desk every morning before breakfast.

And here lies the central paradox of our time. An average human reads at roughly 250 words per minute. If you sat at your desk and read text without pausing, sleeping, or blinking for eight hours straight, you could absorb at most 120,000 words (~160,000 tokens).

If the human retina is already physically overwhelmed by current capacity, why are hyperscalers spending hundreds of billions of dollars deploying millions more GPUs? Where will the trillions of excess tokens actually go?

To answer this, we must inspect four fundamental guideposts: the rigorous first-principles arithmetic of modern inference clusters, the deep historical mechanics of Jevons Paradox, the astronomical appetite of real-time generative video, and radical new direct-to-silicon architectures like Taalas.

1. The First-Principles Arithmetic of Global Token Capacity

To understand the magnitude of the token explosion, we must bypass industry marketing and derive global inference capacity directly from the physical silicon deployed in world datacenters.[1]

Step 1: The Global Accelerator Inventory

Between 2023 and mid-2026, global shipments of high-performance datacenter compute accelerators reached unprecedented scale. By combining historical delivery audits from merchant silicon vendors (NVIDIA Hopper H100/H200, Blackwell B200/GB200, AMD MI300X) with custom hyperscaler ASIC deployments (Google TPU v4/v5e/v5p/v6 Trillium, AWS Trainium 2, Meta MTIA, and domestic Chinese silicon such as Huawei Ascend), we can establish a conservative lower bound for the global active fleet.[2]

  • NVIDIA Hopper Base (H100 / H200): ~1.5 million units shipped in 2023, ~3.6 million units in 2024, and continued deployment through 2025.
  • NVIDIA Blackwell Base (B200 / GB200 NVL72): Ramping aggressively from 2025 through 2026 across major cloud service providers.
  • Hyperscaler Custom Silicon: Over 2.5 million active TPU equivalents deployed across Google datacenters, alongside hundreds of thousands of AWS Trainium/Inferentia and Meta MTIA units.
  • Alternative & Sovereign Merchant Silicon: AMD MI300X/MI325X series (~600,000+ units) plus Ascend and domestic clusters.

Normalized for compute equivalence (using an NVIDIA H100 SXM5 with 3.35 TB/s HBM3 memory bandwidth and 1,979 TFLOPS of dense FP8 Tensor Core compute as a standard unit of measure), the active global installed base sits comfortably between 5.0 million and 7.0 million accelerator equivalents.

For this derivation, let us adopt the conservative baseline: N = 5,000,000 accelerators.

Step 2: The Inference Mechanics of the "Flash" Architecture

Autoregressive Large Language Model inference consists of two fundamentally distinct computational regimes:

  1. The Prefill Phase (Prompt Ingestion): Compute-bound. The entire input prompt is processed in parallel using standard matrix-matrix multiplications (GEMM), achieving near-peak utilization of GPU Tensor Cores.
  2. The Decode Phase (Token Generation): Memory-bandwidth bound. Each subsequent token is generated autoregressively, requiring the GPU to sweep through every parameter weight and Key-Value (KV) cache entry stored in High Bandwidth Memory (HBM) just to produce a single token vector (GEMV).

Under a naive dense 70-billion-parameter model in FP16, generating one token requires streaming 140 gigabytes across the memory bus. On an H100 GPU with 3.35 TB/s memory bandwidth, the physical theoretical single-user generation speed is capped at 3,350 / 140 ≈ 24 tokens/second.

However, the modern "Flash" class of models—exemplified by DeepSeek V3/V4 architectures, Llama-3 8B distillations, and modern speculative Mixture-of-Experts—shatters this ceiling through four compounding microarchitectural breakthroughs:[3]

Architectural Levers of the Modern Flash Tier
  1. Fine-Grained Sparse Routing (MoE): Instead of activating all 30–60 billion parameters, an architecture like DeepSeek uses 256 fine-grained routed experts, activating only 8 per token. The active footprint drops to just ~3.2 billion parameters per token forward pass.
  2. Multi-Head Latent Attention (MLA): Compressing the KV-cache by 4× to 8× into low-rank latent projections, allowing batch sizes to expand by nearly an order of magnitude within the same 80GB HBM pool.
  3. Native FP8/FP4 Microscaling Quantization: Halving the byte footprint per parameter weight, doubling effective arithmetic intensity and memory throughput.
  4. Speculative Multi-Token Decoding: Using ultra-fast parallel draft heads to verify and emit 2.5 to 3.2 tokens per forward step.

Under high-throughput continuous batching frameworks (such as vLLM, TensorRT-LLM, or SGLang) running at server saturation (batch sizes B ≥ 64), an H100 running an MoE Flash model sustains between 800 and 1,500 generated tokens per second per GPU. On next-generation Blackwell GB200 systems featuring FP4 tensor execution and 8.0 TB/s HBM3e bandwidth, sustained throughput routinely exceeds 3,000 tokens per second per chip.

Let us set our sustained inference parameter conservatively at:

Trate = 1,000 tokens / second / accelerator
Sustained generation rate for a saturated FP8 MoE Flash architecture under continuous batching

Step 3: Calculating Global Daily Token Generation

With these physical constants established, we can calculate total global token generation across a single 24-hour cycle:

First-Principles Daily Token Derivation
Global Active AI Accelerators (N) 5,000,000 chips
Sustained Throughput per Chip (Trate) 1,000 tokens/sec
Global Instantaneous Throughput (Φglobal) 5,000,000,000 tokens/sec
Seconds in a Standard Day (S) 86,400 seconds
Total Global Daily Output (Ωday = N × Trate × S) 4.32 × 10¹⁴ tokens/day

The world’s deployed silicon is capable of synthesizing 432,000,000,000,000 tokens every single day.

Step 4: The Per-Capita Distribution

What does 4.32 × 10¹⁴ tokens per day actually mean when distributed across human civilization?

Target Demographic Population Base Daily Token Allotment Daily Word Equivalent Real-World Physical Benchmark
Total Human Population 8.10 Billion 53,333 tok/day ~40,000 words A 130-page non-fiction book per human per day
Global Internet Users 5.40 Billion 80,000 tok/day ~60,000 words George Orwell’s 1984 (full text) every 24 hours
Global Knowledge Workers 1.10 Billion 392,727 tok/day ~294,500 words Half of War and Peace (~587k words) every day
Software Engineers & Researchers 100 Million 4,320,000 tok/day ~3,240,000 words The entire 7-volume Harry Potter series every single day

The physiological discrepancy is stark. The average human reading speed is roughly 250 words per minute (≈ 5.5 tokens/second). A knowledge worker dedicating an entire eight-hour workday to unbroken, continuous reading can process at most:

8 hours × 60 min/hr × 250 words/min × 1.33 tokens/word = 159,600 tokens/day
The absolute physiological ceiling of human reading capacity in a standard 8-hour workday

The deployed compute infrastructure already produces 2.5× more tokens than every knowledge worker on Earth could physically read if they spent their entire working lives doing nothing else. For active software developers, the surplus exceeds 27×.

2. The Historical Parallel: Moon Landings vs. Apple Liquid Glass

There is a recurring cognitive illusion in the history of technology: we assume that when computational power increases, we will simply use it to do our previous serious work faster.

In 1969, computational power was the most precious, scarce, and guarded commodity on the planet. It was dedicated to the most consequential calculation in human history: landing human beings on the surface of another celestial body and returning them safely to Earth.

The Apollo Guidance Computer (AGC)

Designed by the MIT Instrumentation Laboratory under Charles Stark Draper, Eldon Hall, and Margaret Hamilton, and manufactured by Raytheon, the Apollo Guidance Computer (AGC) was the marvel of mid-twentieth-century engineering.[4]

The AGC was the world’s first operational computer built with silicon integrated circuits (using 2,800 dual three-input NOR gate chips from Fairchild Semiconductor). Its technical specifications represent the absolute pinnacle of 1960s aerospace computation:

Apollo 11 Hardware (1969)
Apollo Guidance Computer (AGC)
Master Clock Speed 2.048 MHz (1.024 MHz pulse)
Memory Cycle Time 11.72 microseconds
Instruction Speed ~40,000 – 85,000 IPS
RAM (Magnetic Core) 2,048 words (3.84 KB)
ROM (Core Rope Memory) 36,864 words (69.12 KB)
Power Consumption 55 Watts
Modern Consumer Silicon (2026)
Apple A18 Pro / M4 GPU
FP32 Shader Compute ~4.5 – 38.0 TFLOPS
Memory Bandwidth ~60 – 150 GB/s
Transistor Count ~20 – 28 Billion
Display Refresh 120 Hz ProMotion
Display Subpixels ~11.3 Million (4K/Retina)
Power Consumption ~4 – 15 Watts

The AGC’s responsibilities were staggering. It executed real-time Kalman filtering of rendezvous radar, computed digital autopilot firings for the Reaction Control System (RCS), managed the throttle of the Descent Propulsion System, and maintained inertial navigation state vectors across the entire translunar trajectory.

Let us calculate the total lifetime computation executed by the AGC during the historic Apollo 11 mission:

  • Mission Duration: Launch July 16, 1969 at 13:32:00 UTC to Splashdown July 24, 1969 at 16:50:35 UTC = 195 hours, 18 minutes, 35 seconds (703,115 seconds).
  • Average Instruction Rate: Approximately 50,000 instructions per second (50 kIPS).
  • Total Instructions Executed for Apollo 11:
    IApollo 11 = 703,115 sec × 50,000 inst/sec ≈ 3.515 × 10¹⁰ instructions
    Total operations executed to fly 3 humans 240,000 miles to the lunar surface and return them safely to the Pacific Ocean

Furthermore, the AGC had no hardware floating-point unit; all floating-point vector arithmetic was emulated via software interpreter (developed by Hal Laning), running at roughly 500 FLOPS. The entire lunar landing mission consumed fewer than 3.5 × 10⁸ floating-point calculations.[5]

The Modern UI Shader: Apple’s Liquid Glass and Backdrop Blur

Now, let us examine how modern consumer computing expends its computational riches.

When an iPhone user gently drags their thumb down from the top-right corner of their screen to open the iOS Control Center or unlock their phone, the operating system renders a real-time frosted glass effect (known internally as UIVisualEffectView with UIBlurEffect and UIVibrancyEffect, or the multi-layer specular refraction shaders in visionOS and macOS).[6]

To render that aesthetic frosted blur smoothly at 120 frames per second without stutter, the Apple Metal GPU pipeline executes a complex multi-pass shader graph across millions of pixels:

The Arithmetic Anatomy of an Apple Glass Shader
  1. Bilinear Downsampling Pass: Rendering the background framebuffer to half or quarter resolution via bilinear box filtering (~4 texture fetches, 3 vector additions, 1 multiply per pixel).
  2. Separable Multi-Tap Kawase/Gaussian Blur: A horizontal 1D pass with a 21-tap kernel followed by a vertical 1D pass with a 21-tap kernel. Each tap computes UV coordinates, samples a texture offset, and performs a weighted multiply-accumulate (≈ 42 × 2 = 84 FLOPs/pixel).
  3. Vibrancy & Color Grading Matrix: Transforming RGB color channels through a 3 × 3 saturation boost matrix and a non-linear HDR luminance curve (≈ 20 FLOPs/pixel).
  4. Procedural Noise & Specular Refraction: Sampling a procedural dither texture to eliminate banding artifacts and alpha-compositing over the live video or application buffer (≈ 12 FLOPs/pixel).
  5. Composite Blend: Final interpolation with foreground glyphs and sliders (≈ 6 FLOPs/pixel).

On an iPhone 16 Pro Max display (2868 × 1320 = 3,785,760 pixels), rendering that shader graph across a typical screen region requires approximately 105 floating-point operations per pixel.

Let us calculate the computation required to render that subtle aesthetic effect for just one second:

Φglass = 3,785,760 px × 105 FLOPs/px × 120 frames/sec ≈ 4.77 × 10¹⁰ FLOPs/second
Floating-point arithmetic expended per second to display a translucent frosted blur behind a volume slider

The Stark Comparison

Let us divide the lifetime computational budget of the entire Apollo 11 lunar mission by the compute consumed by your phone’s blur shader:

tequivalence = 3.515 × 10¹⁰ AGC Instructions / 4.77 × 10¹⁰ iPhone Shader FLOPs/sec = 0.737 seconds
Time required for an iPhone GPU to surpass the entire Apollo 11 mission's instruction count
The 0.74-Second Revelation

In less than three-quarters of a single second of you idly dragging down the volume slider on your phone, the graphics processor executes more mathematical operations than the Apollo Guidance Computer performed across all eight days, 195 hours, and 500,000 miles of Apollo 11’s round-trip voyage to the Moon.

If we compare pure floating-point math, the disparity is even more absurd: the iPhone executes the Apollo mission's entire floating-point lifetime total in less than 8 milliseconds—the duration of a single ProMotion display frame.

Did humanity build microprocessors capable of tens of trillions of operations per second because we needed to calculate 100,000 lunar trajectories per second? No. We built them because when compute becomes superabundant, it ceases to be a tool for deliberate arithmetic and becomes an ambient physical medium. We use billions of FLOPs not to solve differential equations, but to create the optical illusion of translucent glass on a handheld piece of capacitive glass.

This exact transformation is now happening to tokens.

3. Jevons Paradox: Why Efficiency Never Conserves Compute

In 1865, British economist and logician William Stanley Jevons published a landmark treatise titled The Coal Question.[7]

At the time, the British Empire was gripped by panic that its industrial dominance would collapse as shallow coal seams were exhausted. Engineers argued that James Watt’s new steam engine—which consumed roughly 75% less coal per unit of mechanical work than Thomas Newcomen’s primitive atmospheric engine—would conserve the nation’s coal reserves.

Jevons observed the exact opposite:

"It is wholly a confusion of ideas to suppose that the economical use of fuel is equivalent to a diminished consumption. The very contrary is the truth... Every improvement of the engine; when effected, does but accelerate anew the consumption of coal."

— William Stanley Jevons, The Coal Question (1865)

Jevons realized that when an engine becomes four times more efficient, you do not use one-fourth the fuel to do the same task. Instead, the cost per horsepower-hour collapses below the economic threshold where steam power becomes profitable for thousands of entirely new industries: steam-powered textile looms, transcontinental coal railways, steamship fleets, and mechanized blast furnaces. Total coal consumption exploded by orders of magnitude.

The Four Historical Computing Iterations of Jevons Paradox

Computing history is a direct, unbroken chain of Jevons Paradox across every physical substrate:

  1. Memory (RAM): When computer memory was hand-threaded magnetic core rope where each bit cost pennies, programs were written in hyper-optimized 4KB assembly loops. When 64GB DDR5 memory became a $120 consumer commodity, software engineers did not write 4KB programs 16 million times faster. We wrapped simple text fields in 500MB Electron desktop runtimes containing full Chromium web engines, V8 JavaScript compilers, virtual DOM diffing trees, and background garbage collection sweeps.
  2. Bandwidth: In the early 1990s over 14.4 kbps acoustic modems, transmitting plain ASCII text required patience. When consumer internet bandwidth scaled 70,000× to 1 Gbps fiber, humanity did not download text files 70,000× faster. We invented 4K 60FPS HDR video streaming, multi-gigabyte game patches, real-time spatial video, and infinite-scroll algorithmic video feeds that consume gigabytes per hour of idle attention.
  3. Storage: In 1956, the IBM 305 RAMAC stored 5 megabytes on fifty 24-inch magnetic disks, weighed over a ton, and leased for $3,200 per month. Today, an 8-terabyte NVMe SSD the size of a stick of gum costs less than $0.05 per gigabyte. We do not store 1.6 million times more census records; we record continuous 4K dashcam loops, uncompressed multi-track audio, and billions of ephemeral photos that no human will ever look at again.
  4. Floating-Point Compute: From room-sized mainframes calculating artillery firing tables to GPUs executing trillions of shader passes to simulate sub-surface skin light scattering and dynamic fluid turbulence in real-time video games.

In every instance, the pattern is identical: whenever the cost of a computational resource drops by three orders of magnitude, the resource transitions from a scarce deliberative calculation to an ambient, throwaway material.

4. The Generative Video Explosion: Replacing Broadcast TV & YouTube

If human text consumption is saturated at 160,000 tokens per day, where will the next three orders of magnitude of consumer token demand originate?

The answer lies in the ultimate media transition: the replacement of static pre-rendered video (Broadcast Television, Netflix, YouTube) with real-time, interactive, personalized generative video.

In modern Spatio-Temporal Diffusion Transformers (DiT) and autoregressive video models (such as Sora, Movie Gen, or Cosmos), video is not treated as flat pixel buffers. It is encoded into discrete 3D spatial-temporal latent tokens using 3D Variational Autoencoders (3D-VAE).[8]

Let us calculate the token generation intensity of real-time video synthesis across standard resolutions:

Video Format & Framerate Spatial Latent Grid (8×8 Patch) Temporal Downsampling Tokens / Second of Video Tokens / Minute of Video
720p HD @ 24 FPS 160 × 90 = 14,400 latents 4× temporal stride 86,400 tok/sec 5.18 Million tok/min
1080p Full HD @ 30 FPS 240 × 135 = 32,400 latents 4× temporal stride 243,000 tok/sec 14.58 Million tok/min
4K UHD @ 60 FPS (Cinematic) 480 × 270 = 129,600 latents 4× temporal stride 1,944,000 tok/sec 116.64 Million tok/min

Now, let us examine what happens when ordinary human leisure time transitions from streaming static MP4 files to real-time generative video:

Daily Entertainment Token Ingestion Scenarios
Scenario A: 30 minutes of generated 720p short-form video (TikTok/Shorts replacement) 155,520,000 tokens / user / day
Scenario B: 2 hours of generated 1080p stream (Personalized TV / YouTube replacement) 1,749,600,000 tokens / user / day
Scenario C: 2 hours of interactive 4K 60FPS cinematic entertainment 13,996,800,000 tokens / user / day

Notice the staggering scale of the transition:

  • A knowledge worker reading text all day consumes 160,000 tokens.
  • A consumer watching just 30 minutes of personalized 720p video consumes 155 million tokens—nearly 1,000× more tokens than a full day of reading.
  • A consumer relaxing in the evening watching 2 hours of personalized 1080p entertainment consumes 1.75 billion tokens.
Ωvideo global = 1,000,000,000 viewers × 1.75 × 10⁹ tok/user = 1.75 × 10¹⁸ tokens / day
Daily token demand if 1 billion global viewers watch 2 hours of personalized 1080p video per day (1.75 Quintillion tokens)

If just 1 billion people replace their evening television with personalized 1080p video synthesis, global demand reaches 1.75 Quintillion tokens per day. That single use case requires 4,000× more compute than the entire world’s currently deployed datacenter capacity.

This is Jevons Paradox in its purest, most visceral form: the moment token generation becomes 100× cheaper, entertainment ceases to be static files stored on AWS S3 and becomes an interactive, infinitely generative visual dreamscape synthesized frame-by-frame for each individual viewer.

5. The Taxonomy of Post-Human Token Consumption

Beyond video entertainment, where do the remaining hundreds of trillions of tokens go in the enterprise and digital economy?

We can categorize the post-human token sink into four primary architectural domains:

1. Test-Time Compute & Reasoning Search Trees (The 10,000:1 Discard Ratio)

The emergence of reasoning models (such as DeepSeek-R1, OpenAI o1/o3, and test-time search algorithms) fundamentally breaks the 1:1 ratio between tokens generated and tokens presented.[9]

When solving a complex formal proof, a competitive programming challenge, or an architectural refactor, a model no longer emits a direct sequence of tokens. Instead, it executes an expansive Monte Carlo Tree Search (MCTS):

  • It generates 50 speculative branches of intermediate reasoning.
  • It backtracks upon discovering logical inconsistencies.
  • It generates automated unit tests, runs them in an internal sandbox, parses compiler errors, and refines its hypotheses.
  • It debates alternative strategies across multiple self-critique heads.

To produce a final, verified 50-token answer (e.g., a one-line kernel fix or a mathematical constant), the cluster generates 500,000 internal reasoning tokens. The generation-to-consumption ratio is 10,000 to 1. The human user never reads the reasoning trace; they only consume the verified output.

2. Autonomous Multi-Agent Feedback Loops & Continuous Refactoring

In traditional software engineering, code is written once and modified only when an active bug or feature request is filed.

In an ambient compute regime, codebases are subjected to continuous background mutation and verification. Swarms of specialized agents operate autonomously across production repositories:

  • Continuous Optimization Agents: Profiling production CPU bottlenecks, rewriting hot loops into SIMD assembly or Rust, compiling the binary, and verifying benchmarks in sandbox containers.
  • Vulnerability Fuzzing Swarms: Continuously generating millions of adversarial API payloads and symbolic execution paths to discover zero-day security vulnerabilities before malicious actors do.
  • Dependency Migration Daemons: Incrementally refactoring legacy codebases across API version updates, running test suites, and resolving merge conflicts autonomously.

A single enterprise engineering organization can easily run a swarm of 500 background agents generating 100 million tokens per hour—without a single human reading a single intermediate log line.

3. Continuous Ambient World Modeling & Spatial Video Ingest

Consider the computational requirements of smart glasses or multimodal edge sensors running continuous vision-language models (VLMs):

Continuous Spatial Video Ingest Math
Camera Ingest Frame Rate 30 frames/sec
Patch Token Density per Frame (16 × 16 grid) 256 visual tokens/frame
Instantaneous Token Generation Rate 7,680 tokens/sec
Waking Hours per User per Day (16 hours) 57,600 seconds
Total Daily Ingest per Single User 442,368,000 tokens/day

A single human wearing multimodal AR glasses for 16 hours a day consumes nearly half a billion tokens per day purely to maintain a real-time semantic index of their surroundings: recognizing faces, transcribing speech, detecting hazards, and maintaining episodic memory.

4. Synthetic Data Factories & Distillation Engines

As frontier AI labs exhaust public human-written internet text, the training pipeline for next-generation models shifts toward synthetic data distillation.

Massive foundation clusters run 24/7 generating petabytes of structured synthetic training corpora: synthetic textbook chapters, verified formal mathematics datasets, multi-turn tool-calling transcripts, and simulated multi-agent game environments. These trillions of generated tokens are never viewed by a human; they are immediately piped into the data loader of a training cluster to optimize a smaller, faster model.

6. Direct-to-Silicon Architecture: Taalas and Hardwired Model Portfolios

To sustain hundreds of trillions—and eventually quintillions—of tokens per day, the physical silicon substrate must undergo a fundamental phase change.

For the past four decades, computing has adhered to the Von Neumann / Stored-Program Architecture: general-purpose processors (CPUs and GPUs) read instruction streams from memory, load data weights from dynamic RAM across high-speed buses, execute arithmetic operations in ALUs, and write results back to memory.

In modern LLM inference, this architecture hits an unyielding physical wall: the Memory Wall. In autoregressive decoding, over 90% of the energy consumed by an NVIDIA H100 or Blackwell GPU is not spent performing matrix math in Tensor Cores—it is spent burning joules to fetch parameter weights across the High Bandwidth Memory (HBM) physical PHY layer.

The Direct-to-Silicon Revolution: Hardwired Model ASICs

Emerging hardware startups like Taalas (founded by former Tenstorrent founder Ljubisa Bajic) are proposing a radical departure from the stored-program GPU paradigm: hardwiring neural network weights directly into the silicon interconnect metallization layers.[10]

  • Zero External DRAM / Zero HBM: The weights of a specific model (e.g. a distilled Llama-3 8B, a DeepSeek 3B active MoE expert, or an embedding model) are physically printed as hardwired metal wiring masks during chip fabrication.
  • Wavefront Feedforward Inference: Because the weights never need to be fetched from memory, the token activations simply flow through a continuous cascade of hardwired arithmetic gates across the silicon die at clock speed.
  • 100× Energy Efficiency: Eliminating HBM memory transfers collapses energy consumption per token from ~10–50 microjoules on a GPU down to sub-microjoules.
  • 1,000× Latency Reduction: Time-to-first-token and time-per-output-token drop to microseconds.

How does this transform the economics of serving base models?

In a world dominated by general-purpose GPUs, serving a diverse portfolio of models requires expensive, power-hungry clusters that must constantly swap models in and out of HBM.

Under direct-to-silicon economics, hyperscalers and enterprises will deploy modular racks of specialized, hardwired model dies:

Current Paradigm (General GPU Cluster)
HBM-Bound Dynamic Serving
Silicon Architecture General-purpose Tensor Cores + HBM3e
Energy Bottleneck ~90% power in memory interconnects
Hardware Unit Cost $30,000 – $45,000 per accelerator
Throughput / Watt ~2 – 5 tokens / second / watt
Model Flexibility Fully programmable (any weights)
Direct-to-Silicon Paradigm (Taalas ASIC)
Hardwired Model Portfolios
Silicon Architecture Weights metal-etched into silicon wiring
Energy Bottleneck Pure arithmetic switching (zero DRAM)
Hardware Unit Cost ~$500 – $2,000 per dedicated ASIC die
Throughput / Watt ~200 – 500 tokens / second / watt
Model Flexibility Frozen base model portfolio per die

Consider a future datacenter serving a standardized portfolio of foundational base models:

  1. A 3B Routing & Grammar ASIC (processing 100,000 tokens/sec at 15 Watts).
  2. An 8B Code Generation & Refactoring ASIC (processing 50,000 tokens/sec at 25 Watts).
  3. A 14B Symbolic Math & Verification ASIC (processing 30,000 tokens/sec at 40 Watts).
  4. A 3D Video Latent Synthesis ASIC (synthesizing 1080p video at 60 FPS in real-time at 50 Watts).

When frozen base models can be mass-manufactured into dedicated silicon for a few hundred dollars per chip, the marginal cost of structured reasoning drops below the cost of municipal electricity. Intelligence ceases to be a cloud service billed per query; it becomes a hardwired physical property of the electronic circuits themselves.

7. Interactive Simulator: Global Token & Compute Capacity

Use the interactive simulator below to explore how changes in deployed accelerator counts, model architectures, target populations, and workload distributions alter global token generation and historical FLOP multipliers.

Global Token & Compute Capacity Simulator
Adjust hardware parameters and workload allocations to see real-time per-capita token allotments and historical compute equivalences.
Active AI Accelerators (Millions) 5.0 M
Throughput / Chip (Tokens / Sec) 1,000 tok/s
Target Population Distribution Knowledge Workers (1.1B)
Reasoning Search / Discard Ratio 1 : 1 (Direct)
Daily Global Tokens
432 T
5.0 Billion tokens / sec
Daily Tokens / Person
392,727
~294,545 words / day
Daily Book Equiv.
6.3
Copies of Great Gatsby / day
Apollo 11 Missions
853,485,064×
Apollo missions' FLOPs / sec

8. The Economics of the Inference Plateau

The relentless scaling of inference efficiency is precipitating a structural shift in technology economics.

Between 2020 and 2024, competitive advantage was defined almost entirely by training capital expenditure: who could amass 50,000 GPUs to pre-train the next 500-billion-parameter foundation model.

Today, the economic gravity has inverted toward inference operations. A foundation model is trained once over a three-month window; its distilled derivatives run continuously across millions of servers for years.[11]

Era / Milestone Representative Model Typical Cost / Million Tokens Dominant Consumption Paradigm
Early Frontier Era (2023) GPT-4 (Original) $30.00 – $60.00 Synchronous chat, human-in-the-loop editing
Early Distillation Era (2024) GPT-4o mini / Claude 3.5 Haiku $0.25 – $1.00 Document batch processing, basic customer routing
Open-Weights Sparse MoE (2025) DeepSeek V3 / Llama 3.3 70B $0.10 – $0.28 Autonomous coding agents, unit-test verification
Micro-Quantized Flash Tier (2026) DeepSeek V4 Flash / FP4 MoE $0.02 – $0.05 Continuous ambient video ingest, speculative MCTS search
Direct-to-Silicon ASIC Era (Future) Taalas Hardwired Base Portfolios < $0.001 Real-time 4K generative video, continuous ambient cognition

When intelligence costs less than $0.001 per million tokens, the cost of generating a complete, error-checked software system drops below the cost of routing a packet across the public internet.

The bottleneck ceases to be computational cost. The new bottlenecks become verification latency, systemic memory coherence, and physical actuator throughput in the real world.

9. Conclusion: The Semantic Texture of the World

Civilization advances by turning miraculous, once-in-a-generation engineering achievements into invisible, background plumbing.

In 1969, the Apollo Guidance Computer was an almost sacred object. It demanded the full attention of the world’s greatest engineers, required thousands of hours of hand-woven rope memory assembly, and consumed a non-trivial fraction of the national aerospace budget to perform 50,000 calculations per second.

Today, an iPhone casually executes forty-five billion operations every second just to render a translucent blur behind an alarm clock notification on a lock screen. We do not marvel at the mathematics of the separable Kawase blur pass; we complain if the animation stutters by a single frame.

The token is undergoing the exact same historical metamorphosis.

We are rapidly moving past the era where a token is a precious message typed by an artificial oracle for human contemplation. As global capacity surges past 400 trillion tokens per day—and as real-time generative video and hardwired ASICs push us toward quintillions—tokens are becoming the invisible, ambient texture of the digital universe.

Trillions of tokens will be generated to explore dead-end branches of mathematical search trees. Trillions more will be generated to synthesize bespoke, photorealistic 4K video streams for evening leisure. Hundreds of trillions will be burned continuously by ambient cameras and microphones translating the physical reality of human life into structured semantic memory.

Just as Jevons realized that cheaper coal would build the modern industrial world, the collapse in token costs will not conserve compute. It will build an ambient cognitive substrate—where structured intelligence, like electricity and running water, is simply too abundant to notice.

Footnotes & References

  1. Methodology & Compute Tracking: Installed base estimates synthesized from SemiAnalysis datacenter hardware tracker reports (2024–2026), Epoch AI compute scaling audits, and Top500 accelerator statistics. ↩
  2. NVIDIA & Merchant Accelerator Shipments: NVIDIA quarterly 10-Q/10-K financial reports (FY2024–FY2026), TSMC CoWoS packaging capacity expansion schedules, and merchant H100/H200/B200 shipment surveys. ↩
  3. DeepSeek Architecture & MLA: DeepSeek-AI, DeepSeek-V3 Technical Report (2024) and DeepSeek-R1: Incentivizing Reasoning Capability in LLMs via Reinforcement Learning (2025). Detailing Multi-Head Latent Attention (MLA), 256 fine-grained MoE routing, and FP8 mixed-precision training/inference.
  4. Apollo Guidance Computer Architecture: Eldon C. Hall, Journey to the Moon: The History of the Apollo Guidance Computer, AIAA (1996); MIT Instrumentation Laboratory Report R-700; David A. Mindell, Digital Apollo: Human and Machine in Spaceflight, MIT Press (2008).
  5. AGC Mission Arithmetic: Calculations based on Apollo 11 Mission Timeline (NASA Mission Report SP-238). Flight duration: 195h 18m 35s. Average instruction rate: 43.4–85.2 kIPS across typical job loop mixes.
  6. GPU Shader Mathematics: Apple Developer Documentation, Metal Shading Language Specification (v3.1); Masaki Kawase, Frame Buffer Post-processing Effects in Double-S.T.E.A.L., Game Developers Conference (2003); ARM Mali GPU Architecture Best Practices for Real-Time Blurs.
  7. Jevons Paradox: William Stanley Jevons, The Coal Question: An Inquiry Concerning the Progress of the Nation, and the Probable Exhaustion of Our Coal-Mines, Macmillan and Co., London (1865).
  8. Spatio-Temporal Video Tokenization: OpenAI, Video Generation Models as World Simulators (Sora Report, 2024); Meta AI, Movie Gen: A Cast of Media Foundation Models (2024); NVIDIA, Cosmos World Foundation Model Platform (2025).
  9. Test-Time Compute & Reasoning Scaling: Noam Brown et al., Large Language Monkeys: Scaling Inference Compute with Verifiers (2024); OpenAI, Learning to Reason with LLMs (o1 system paper, 2024).
  10. Direct-to-Silicon Model ASICs: Taalas Semiconductor Whitepaper (2024–2025), Direct-to-Silicon Neural Network Implementation: Eliminating the HBM Memory Wall via Metal-Layer Weight Hardwiring; Ljubisa Bajic, Architecture Keynotes.
  11. Inference Economics & Energy Scaling: SemiAnalysis, The Economics of AI Inference vs Training (2025); Landauer's Principle thermodynamic limits (kB T ln 2).