The Economics of Sparse Compute.

Why 671B total and 37B active change FLOPs, memory, communication, utilization, serving, and cost in different ways.

This chapter follows the series' four-layer pyramid: intuition first, then consequences, system design, and finally implementation-level checks. It is written to be useful both as a first explanation and as a review sheet before reading the primary papers.

What you should be able to do after reading

• Explain the mechanism without relying on the feature name.
• Trace the relevant tensors, losses, or messages through one concrete example.
• Distinguish a paper claim from an inference, implementation choice, or marketing shorthand.
• Design a minimal experiment that could prove the idea wrong.

Where this chapter fits in the ten-phase map

The V2/V3 system stack is where the earlier components stop being independent diagrams. MLA changes cache traffic, MoE changes network traffic, MTP changes the training graph, and FP8 changes numerical and kernel contracts. Parallel schedules must accommodate all four at once.

The dependency is useful when debugging. If the model-level equation is correct but the measured result is poor, walk backward through representation, numerical format, memory layout, routing or communication, and finally the evaluation harness. The first broken contract is usually more actionable than the final benchmark delta.

1. Active parameters approximate arithmetic

Only selected routed experts execute for a token, so FFN FLOPs track active rather than total expert parameters. Attention and dense layers remain active, making the relationship approximate rather than exact.

2. Total parameters determine storage

All experts must be available across the expert-parallel pool. A 671B checkpoint needs storage, load time, optimizer state during training, and enough aggregate accelerator memory even though one token touches a small fraction.

3. Communication becomes a new tax

Tokens must travel to expert-owning devices and return. All-to-all bandwidth, synchronization, padding, and routing imbalance can erase theoretical FLOP savings. Sparse arithmetic only wins if the network and kernels keep experts fed.

4. Serving has utilization tradeoffs

Large batches spread tokens across experts and improve utilization, while small batches leave many expert matrices underfilled. Replicating popular experts improves latency but consumes more memory. Capacity planning must consider request mix and context length.

5. Cost claims require a denominator

Training GPU hours, rental rates, amortized hardware, energy, networking, data, experimentation, and post-training are different cost concepts. A published pretraining estimate should never be presented as the complete cost of creating a model.

Engineering lens. For every concept above, identify the tensor, state, metric, or system boundary that makes it observable. Then ask which assumption would make the claim fail. This keeps the chapter testable instead of leaving it as architecture vocabulary.

Worked example

Compare a 37B dense model with a 671B/37B-active MoE. Give both equal token FLOPs, then add expert weight memory, all-to-all bytes, and utilization. Identify batch sizes where the dense model can be faster despite similar arithmetic.

Do the arithmetic with small dimensions first. Small examples expose index shifts, hidden assumptions, and missing denominators that disappear inside a billion-parameter headline. Once the hand-worked result is correct, automate it and compare the program output against the same values.

Implementation and measurement plan

Model cost per request from prefill/decode separately. Include model replicas, KV cache, expert parallel group size, network topology, and tail latency. Validate the model with profiler traces, not only theoretical FLOPs.

1. State the exact model, checkpoint, hardware, and date behind every numerical claim.
2. Separate algorithmic complexity, theoretical FLOPs, measured latency, memory, and end-to-end cost.
3. Build a small reference implementation before optimizing kernels or distributing it.
4. Compare against an equal-compute or equal-parameter baseline and report the denominator.
5. Record failure cases and scope limits beside the successful result.

From a paper claim to an engineering contract

The primary anchor for this chapter is DeepSeek-V2 Technical Report from DeepSeek-V2. Reading a number from that source is only the first step. A reproducible contract has four layers:

Layer	Question to write down	Evidence
Mechanism	What operation, loss, state, or routing decision changes?	Equation, pseudocode, tensor shapes
Implementation	How is it realized on the named hardware and software stack?	Kernel, precision, layout, process groups
Measurement	Which denominator and baseline make the comparison fair?	Raw metrics, config, repeated runs
Scope	Where should the claim stop being trusted?	Failure cases, ablations, dated limitations

This separation prevents a frequent error in frontier-model writing: converting a theoretical reduction into a latency promise, or converting one internal benchmark into a universal quality ranking. The implementation can fail to realize the algorithm, and the workload can fail to expose the intended benefit.

Failure modes and misleading shortcuts

• Active parameters are not a precise latency predictor.
• Sparse models still store every expert.
• Headline rental cost omits experimentation and post-training.
• Low average load can hide hot experts.
• More experts can reduce GEMM efficiency.

These are not footnotes. Frontier-model engineering is dominated by boundary conditions: a method can be mathematically correct and still lose to memory traffic, data skew, numerical drift, evaluation leakage, or a poorly stated comparison. A credible result makes those boundaries visible.

How to audit claims about this topic

Rewrite each claim with its missing boundary: name the exact mechanism, identify the tensor or resource it changes, and attach the workload and measurement. Then construct a counterexample at the edge of the claim. If a sentence cannot survive that rewrite, treat it as orientation—not evidence.

Next, trace provenance. Prefer the primary report for configuration and results, the released code for implementation behavior, and your own profiler for product performance. Secondary explainers are valuable for intuition but should not silently become the source of a numerical claim.

Decision guide: when should you use this idea?

Use it when the bottleneck named in the thesis appears in profiler traces or controlled quality experiments, the necessary kernels and runtime support exist, and the added system complexity can be observed in production. Start with the smallest configuration that exposes the bottleneck.

Delay it when a dense or higher-precision baseline does not yet converge, the evaluation harness is unstable, or the claimed resource is not limiting the workload. Sophisticated architecture cannot compensate for an invalid baseline.

Reject it when its benefit exists only under a denominator irrelevant to the product—for example, theoretical FLOPs while user latency worsens—or when numerical, safety, or operational regressions exceed the measured gain.

Hands-on study lab

1. 1. Build a full cost worksheet.
2. 2. Measure expert occupancy by batch size.
3. 3. Separate capex and marginal cost.
4. 4. Find the break-even network bandwidth.

For each exercise, save the configuration, a tiny deterministic fixture, the raw measurements, and one failed case. The goal is not merely to make the code run; it is to make the conclusion independently checkable.

Quick self-check

What is the central idea?

MoE decouples learned capacity from per-token arithmetic, but it does not make inactive parameters free: weights, routing, communication, and uneven utilization still determine the bill.

What is the most common reading mistake?

Active parameters are not a precise latency predictor.

What evidence should I demand?

An exact configuration, a fair baseline, primary-source support, end-to-end measurements, and failure cases at the limits of the claim.

How do I explain it to a new engineer?

Begin with the bottleneck, show one tiny worked example, trace the changed state, and only then introduce the official name. Finish by naming one situation where the method will not help.

How do I review an implementation?

Check indexing and masks, parameter sharing, dtype transitions, layouts, process-group scope, raw metric denominators, and behavior under an adversarial or worst-case fixture. A passing happy-path shape test is not enough.

Teach-back synthesis

Close the page and reconstruct the argument in five sentences: the bottleneck; the mechanism; the state or tensor that changes; the fair measurement; and the main failure mode. Then reopen the page and compare. If you can repeat the feature names but cannot state those five sentences, revisit the worked example.

Finally, connect the idea to two neighboring phases. DeepSeek's advantage is not one isolated invention: compressed attention changes the cache, sparse experts change active compute, FP8 changes arithmetic and bandwidth, distributed schedules hide communication, and reasoning training spends the resulting capacity differently. The series becomes useful when those dependencies form one mental model.

Key takeaways

• Why 671B total and 37B active change FLOPs, memory, communication, utilization, serving, and cost in different ways.
• The mechanism, training recipe, runtime implementation, and measured product behavior are separate layers of evidence.
• Numbers remain meaningful only with their workload, precision, hardware, context length, and date attached.
• A small reproducible test is more valuable than a large uncheckable diagram.

Primary sources and further reading

• DeepSeek-V2. DeepSeek-V2 Technical Report.
• DeepSeek-V3. DeepSeek-V3 Technical Report.
• Rajbhandari et al.. ZeRO: Memory Optimizations Toward Training Trillion Parameter Models.

Source note: explanations and worked examples here are original. Numerical claims are scoped to the linked reports; rapidly changing model comparisons are dated in the article itself.