6.4.10 · D4Power, Thermal & Reliability

Exercises — Energy efficiency (performance per watt)

3,377 words15 min readBack to topic

Symbols used everywhere below (all defined in the parent, restated here so nothing is assumed):


Level 1 — Recognition

Recall Solution 1.1

WHAT: Performance per watt is just performance divided by power. WHY: The definition fuses the two numbers into one honest score. Answer: .

Recall Solution 1.2

  • = activity factor (fraction of gates flipping),
  • = switched capacitance,
  • = supply voltage (appears squared — this matters later),
  • = clock frequency. Mnemonic from the parent: "Alpha Cats Voltage-Squared Frequency."
Recall Solution 1.3

Operations per joule. Performance is work-per-second and power is energy-per-second; the "per second" cancels: So perf/watt tells you the total work squeezable from a fixed energy budget (a battery).


Level 2 — Application

Recall Solution 2.1

(a) First divide performance by power: Now convert to the requested GFLOPS/W. The prefix "G" (giga) means , so . To express our number in those units we divide by : (b) Energy per FLOP is the reciprocal of ops-per-joule (note FLOP/(s·W) = FLOP/J): WHY the reciprocal: ops/joule flipped upside-down gives joules/op — confirming perf/watt ≡ work/energy.

Recall Solution 2.2

WHAT: We only need relative factors, so plug ratios into . Answer: , i.e. about of the original dynamic power. WHY: and are unchanged, so they cancel in the ratio — only moves.

Recall Solution 2.3

Recall is the always-on trickle current from the cast of symbols. Static power is just that current pushed by the voltage: Total . Leakage share . This is why "only dynamic power matters" is false in deep-nanometer chips.


Level 3 — Analysis

The figure below plots two side-by-side bars per chip for the exercise that follows: a burnt-orange bar = raw speed in GFLOPS, and a teal bar = perf/watt in GFLOPS/W. Because perf/watt (2–2.5) is a tiny number next to the GFLOPS values (120–200), we multiply the teal bars by 50 purely so they are tall enough to see next to the orange ones — a display trick, nothing physical. Since both teal bars are scaled by the same factor 50, their relative heights are still honest: a taller teal bar still means genuinely higher perf/watt. The printed number above each teal bar is the true unscaled value.

Figure — Energy efficiency (performance per watt)
Recall Solution 3.1

A: . B: . Efficiency: A wins () — more work per joule. Speed: B wins ( GFLOPS raw). Not the same answer. Faster ≠ more efficient. For a battery/thermal-limited device pick A; for raw throughput where power is free, pick B. In the figure above, B's orange (speed) bar is taller, but its teal (perf/watt) bar is shorter than A's — remember the teal bars are both ×50 for visibility, so it's their relative height that carries the message, and A's teal is genuinely taller.

Recall Solution 3.2

WHY : performance , but under scaling power , so perf/watt . Perf/watt falls to of its original value — a drop for a mere speed gain. That asymmetry is why clock-only scaling died and we moved to multicore.

Recall Solution 3.3

WHAT: Total energy = power × time.

  • X: .
  • Y: . Y uses less energy (), even though it's slower. WHY the fast one lost: X needed higher and ; power () rose faster than the time fell. Finishing sooner does not guarantee less energy.

Level 4 — Synthesis

Recall Solution 4.1

New dynamic: ratio . New static: (with the fixed leakage current from the cast of symbols), and dropped by : New total: (was ). Performance tracks : ratio . Perf/watt improvement . WHY only moves for dynamic: . Here (activity) and (the fixed silicon capacitance) do not change under DVFS — the same gates switch on the same transistors — so they appear identically in the "before" and "after" and cancel when we take the ratio. Only and actually move, leaving . WHY static scales only as : , and with held constant here, static power is linear in — one factor of , not squared — so it shrinks less aggressively than dynamic. Answer: total power ; perf/watt up by for only less speed. Note leakage dilutes the pure-dynamic gain (compare Ex. 2.2's where leakage was ignored).

Recall Solution 4.2

Throughput check (cores × frequency): single = ; dual = . Equal throughput.WHY cancels again: every core is the same silicon design, so and are identical across all cores and across both options — they factor out of the comparison, leaving each core's dynamic power . Single-core dynamic (, ): (units of ). Two-core dynamic (, , two cores): Ratio . Answer: same throughput at of the dynamic power — the multicore win, straight from . Two slow cores beat one fast core because each runs at lower voltage.


Level 5 — Mastery

Recall Solution 5.1

Set up total power as a function of . Substitute : Cap at 5 W: solve . Try : (just under). Try : . So — comfortably above , so the simple model is valid here. Perf/watt. Performance , and by the stated one-op-per-tick assumption corresponds to ; power is at the cap: WHY it matters: the cube term dominates near the ceiling — squeezing the last MHz costs disproportionate power, exactly why phones throttle. Answer: , perf/watt .

Recall Solution 5.2

WHAT we optimise: perf/watt (cancel one ). WHY the derivative tool: to find the maximum of a smooth function we ask where its slope is zero — that's what a derivative finds. This is negative for all and zero only at : efficiency monotonically decreases as rises. So within this simple model the theoretical peak sits at the lowest possible voltage (, efficiency ). WHY real chips don't sit there — three reasons:

  1. Frequency dies. , so the chip becomes maximally efficient but does almost no work per second — it can never meet a deadline. Efficiency (ops/joule) and usefulness (ops/second) pull in opposite directions.
  2. The model breaks below . Once approaches the threshold voltage, transistors enter the subthreshold region: no longer holds (speed collapses faster than linearly) and the constant- assumption fails — leakage rises exponentially, so per unit work explodes rather than shrinking. The pretty curve simply is not valid there.
  3. Leakage per second is fixed overhead. Dragging a job out at low keeps the chip powered for longer, and drains energy every second it's on — so beyond a point lowering voltage can raise total energy for a fixed task. Conclusion: real design targets the ==lowest voltage that still meets the performance deadline and stays safely above == — a constrained optimum, never the mathematical peak.

The figure below draws both curves from this problem on one voltage axis: the teal curve is perf/watt (falling everywhere, confirming Ex. 5.2), and the burnt-orange curve is total power (exploding as climbs). The plum dashed line marks the TDP cap from Ex. 5.1, and the plum dot is the solution , . The grey shaded band on the left marks the sub-threshold danger zone () where the simple model is no longer valid — read curves only to the right of it.

Figure — Energy efficiency (performance per watt)
Recall Solution 5.3

Energy = power × time, summed over nodes.

  • P: .
  • Q: . Energy winner: Q (). Time winner: Q too (). Here Q wins on both — the low-clock nodes (lower , so savings) more than pay for the extra nodes. Trade-off statement: wide-and-slow (more nodes at lower voltage) usually beats narrow-and-fast on energy, and here even on time because 8 nodes parallelise the work; the only cost Q pays is higher up-front hardware and more total idle/static power (8 chips each leak whenever they idle), which is the reliability and capital-cost dimension the pure energy sum quietly hides. So: pick Q for this job, but if node cost or leakage-at-idle dominated your budget, the comparison could flip.

Wrap-up recall