WHAT: Performance per watt is just performance divided by power.
WHY: The definition PowerPerf fuses the two numbers into one honest score.
20W40GFLOPS=2GFLOPS/W.Answer: 2GFLOPS/W.
Recall Solution 1.2
Pdyn=αCV2f.
α = activity factor (fraction of gates flipping),
C = switched capacitance,
V = supply voltage (appears squared — this matters later),
f = 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:
energy/swork/s=energywork=jouleops.
So perf/watt tells you the total work squeezable from a fixed energy budget (a battery).
(a) First divide performance by power:
300W60×1012FLOP/s=2×1011FLOP/(s⋅W).
Now convert to the requested GFLOPS/W. The prefix "G" (giga) means 109, so 1GFLOPS/W=109FLOP/(s⋅W). To express our number in those units we divide by 109:
2×1011FLOP/(s⋅W)=1092×1011GFLOPS/W=200GFLOPS/W.(b) Energy per FLOP is the reciprocal of ops-per-joule (note FLOP/(s·W) = FLOP/J):
2×1011FLOP/J1=5×10−12J=5pJ/FLOP.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 Pdyn∝V2f.
(1.20.9)2×32.25=(0.75)2×0.75=0.5625×0.75=0.4218…Answer: ≈0.4219, i.e. about 42.2% of the original dynamic power.WHY:α and C are unchanged, so they cancel in the ratio — only V2f moves.
Recall Solution 2.3
Recall Ileak is the always-on trickle current from the cast of symbols. Static power is just that current pushed by the voltage:
Pstat=VIleak=1.0×2=2W.
Total =Pdyn+Pstat=8+2=10W.
Leakage share =102=20%.
This is why "only dynamic power matters" is false in deep-nanometer chips.
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.
Recall Solution 3.1
A:120/48=2.5GFLOPS/W. B:200/100=2.0GFLOPS/W.
Efficiency: A wins (2.5>2.0) — more work per joule.
Speed: B wins (200>120 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 1/f2: performance ∝f, but under V∝f scaling power ∝f3, so perf/watt ∝f/f3=1/f2.
1.2521=1.56251=0.64.
Perf/watt falls to 64% of its original value — a 36% drop for a mere 25% 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: 60W×10s=600J.
Y: 30W×16s=480J.
Y uses less energy (480<600J), even though it's slower.
WHY the fast one lost: X needed higher V and f; power (∝V2f) rose faster than the time fell. Finishing sooner does not guarantee less energy.
New dynamic: ratio =(0.8)2×(1.6/2.0)=0.64×0.8=0.512.
Pdyn′=10×0.512=5.12W.New static:Pstat=VIleak (with Ileak the fixed leakage current from the cast of symbols), and V dropped by 0.8:
Pstat′=2×0.8=1.6W.New total:5.12+1.6=6.72W (was 12W).
Performance tracks f: ratio =1.6/2.0=0.8.
Perf/watt improvement=power ratioperf ratio=6.72/120.8=0.560.8=1.4286.
WHY only V2f moves for dynamic:Pdyn=αCV2f. Here α (activity) and C (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 V and f actually move, leaving V2f.
WHY static scales only as V:Pstat=VIleak, and with Ileak held constant here, static power is linear in V — one factor of V, not squared — so it shrinks less aggressively than dynamic.
Answer: total power 6.72W; perf/watt up by ≈42.9% for only 20% less speed. Note leakage dilutes the pure-dynamic gain (compare Ex. 2.2's 56% where leakage was ignored).
Recall Solution 4.2
Throughput check (cores × frequency): single = 1×3GHz=3.0; dual = 2×1.5GHz=3.0. Equal throughput. ✓
WHY αC cancels again: every core is the same silicon design, so α and C are identical across all cores and across both options — they factor out of the comparison, leaving each core's dynamic power ∝V2f.
Single-core dynamic (V=1.0, f=3): ∝1.02×3=3.0 (units of αC⋅V2f).
Two-core dynamic (V=0.75, f=1.5, two cores):
2×(0.752×1.5)=2×(0.5625×1.5)=2×0.84375=1.6875.
Ratio =1.6875/3.0=0.5625.
Answer: same throughput at ≈56.25% of the dynamic power — the multicore win, straight from V2. Two slow cores beat one fast core because each runs at lower voltage.
Set up total power as a function of V. Substitute f=2V:
P(V)=0.5⋅V2⋅(2V)+V⋅1.0=V3+V.Cap at 5 W: solve V3+V=5.
Try V=1.5: 3.375+1.5=4.875 (just under). Try V=1.52: 3.511+1.52=5.03. So V≈1.5157V — comfortably above Vth, so the simple model is valid here.
V∗≈1.5157V⇒f=2V≈3.031GHz.Perf/watt. Performance ∝f, and by the stated one-op-per-tick assumption f=3.031GHz corresponds to 3.031GFLOPS; power is 5W at the cap:
5W3.031GFLOPS≈0.606GFLOPS/W.WHY it matters: the cube term V3 dominates near the ceiling — squeezing the last MHz costs disproportionate power, exactly why phones throttle. Answer: f≈3.03GHz, perf/watt ≈0.61GFLOPS/W.
Recall Solution 5.2
WHAT we optimise: perf/watt =V3+V2V=V2+12 (cancel one V).
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.
dVd(V2+12)=(V2+1)2−2⋅2V=(V2+1)2−4V.
This is negative for all V>0 and zero only at V=0: efficiency V2+12monotonically decreases as V rises. So within this simple model the theoretical peak sits at the lowest possible voltage (V→0+, efficiency →2).
WHY real chips don't sit there — three reasons:
Frequency dies.f=2V→0, 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.
The model breaks below Vth. Once V approaches the threshold voltage, transistors enter the subthreshold region: f∝V no longer holds (speed collapses faster than linearly) and the constant-Ileak assumption fails — leakage rises exponentially, so Pstat per unit work explodes rather than shrinking. The pretty 2/(V2+1) curve simply is not valid there.
Leakage per second is fixed overhead. Dragging a job out at low f keeps the chip powered for longer, and Pstat=VIleak 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 Vth== — a constrained optimum, never the mathematical V→0 peak.
The figure below draws both curves from this problem on one voltage axis: the teal curve is perf/watt=2/(V2+1) (falling everywhere, confirming Ex. 5.2), and the burnt-orange curve is total powerV3+V (exploding as V climbs). The plum dashed line marks the 5W TDP cap from Ex. 5.1, and the plum dot is the solution V∗≈1.52V, f≈3.03GHz. The grey shaded band on the left marks the sub-threshold danger zone (V<Vth) where the simple model is no longer valid — read curves only to the right of it.
Recall Solution 5.3
Energy = power × time, summed over nodes.
P: 4×250W×2h=2000Wh=2.0kWh.
Q: 8×150W×1.5h=1800Wh=1.8kWh.
Energy winner: Q (1.8<2.0kWh).Time winner: Q too (1.5h<2h).
Here Q wins on both — the low-clock nodes (lower V, so V2 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 VIleak 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.