WHAT: Performance per watt bas performance ko power se divide karna hai.
WHY: Definition PowerPerf dono numbers ko ek honest score mein fuse kar deti hai.
20W40GFLOPS=2GFLOPS/W.Answer: 2GFLOPS/W.
Recall Solution 1.2
Pdyn=αCV2f.
α = activity factor (gates ka fraction jo flip ho raha hai),
C = switched capacitance,
V = supply voltage (squared appear hota hai — yeh baad mein matter karega),
f = clock frequency.
Parent se mnemonic: "Alpha Cats Voltage-Squared Frequency."
Recall Solution 1.3
Operations per joule. Performance hai work-per-second aur power hai energy-per-second; "per second" cancel ho jaata hai:
energy/swork/s=energywork=jouleops.
Toh perf/watt batata hai ki ek fixed energy budget (battery) se kitna total work nikala ja sakta hai.
(a) Pehle performance ko power se divide karo:
300W60×1012FLOP/s=2×1011FLOP/(s⋅W).
Ab requested GFLOPS/W mein convert karo. Prefix "G" (giga) matlab 109 hai, toh 1GFLOPS/W=109FLOP/(s⋅W). Apna number un units mein express karne ke liye 109 se divide karo:
2×1011FLOP/(s⋅W)=1092×1011GFLOPS/W=200GFLOPS/W.(b) Energy per FLOP ops-per-joule ka reciprocal hai (note karo FLOP/(s·W) = FLOP/J):
2×1011FLOP/J1=5×10−12J=5pJ/FLOP.WHY reciprocal: ops/joule ko ulta karo to milta hai joules/op — confirm hota hai ki perf/watt ≡ work/energy.
Recall Solution 2.2
WHAT: Humein sirf relative factors chahiye, toh Pdyn∝V2f mein ratios daalo.
(1.20.9)2×32.25=(0.75)2×0.75=0.5625×0.75=0.4218…Answer: ≈0.4219, yani original dynamic power ka lagbhag 42.2%.WHY:α aur C unchanged hain, toh woh ratio mein cancel ho jaate hain — sirf V2f move karta hai.
Recall Solution 2.3
Yaad karo Ileak symbols ki list se woh always-on trickle current hai. Static power bas woh current hai jo voltage se push hoti hai:
Pstat=VIleak=1.0×2=2W.
Total =Pdyn+Pstat=8+2=10W.
Leakage share =102=20%.
Isliye "sirf dynamic power matter karti hai" deep-nanometer chips mein galat hai.
Neeche ki figure mein aane wali exercise ke liye har chip ke liye side-by-side do bars plot kiye hain: burnt-orange bar = raw speed in GFLOPS, aur teal bar = perf/watt in GFLOPS/W. Kyunki perf/watt (2–2.5) ek bahut chhota number hai GFLOPS values (120–200) ke paas, hum teal bars ko 50 se multiply karte hain sirf isliye taaki woh orange ones ke paas dikhne layak tall hon — yeh ek display trick hai, koi physical cheez nahi. Kyunki dono teal bars same factor 50 se scale kiye gaye hain, unki relative heights phir bhi honest hain: ek taller teal bar genuinely higher perf/watt matlab rakhta hai. Har teal bar ke upar printed number sach mein unscaled value hai.
Recall Solution 3.1
A:120/48=2.5GFLOPS/W. B:200/100=2.0GFLOPS/W.
Efficiency: A jeet ta hai (2.5>2.0) — har joule mein zyada kaam.
Speed: B jeetta hai (200>120 GFLOPS raw).
Same answer nahi hai. Faster ≠ more efficient. Battery/thermal-limited device ke liye A chuno; raw throughput ke liye jahan power free ho, B chuno. Upar ki figure mein, B ka orange (speed) bar taller hai, lekin uska teal (perf/watt) bar A se shorter hai — yaad raho teal bars dono ×50 hain visibility ke liye, toh unki relative height hi message carry karti hai, aur A ka teal genuinely taller hai.
Recall Solution 3.2
WHY 1/f2: performance ∝f hai, lekin V∝f scaling ke under power ∝f3 hai, toh perf/watt ∝f/f3=1/f2.
1.2521=1.56251=0.64.
Perf/watt apni original value ke 64% tak gir jaati hai — sirf 25% speed gain ke liye 36% drop. Woh asymmetry hi wajah hai kyun clock-only scaling khatam hui aur hum multicore ki taraf gaye.
Recall Solution 3.3
WHAT: Total energy = power × time.
X: 60W×10s=600J.
Y: 30W×16s=480J.
Y kam energy use karta hai (480<600J), bhale hi slower ho.
WHY fast wala haara: X ko higher V aur f chahiye tha; power (∝V2f) time se zyada tezi se badhi. Jaldi khatam karna guarantee nahi karta ki energy bhi kam lagegi.
Naya dynamic: ratio =(0.8)2×(1.6/2.0)=0.64×0.8=0.512.
Pdyn′=10×0.512=5.12W.Naya static:Pstat=VIleak (symbols ki list se fixed leakage current Ileak ke saath), aur V0.8 se gira:
Pstat′=2×0.8=1.6W.Naya total:5.12+1.6=6.72W (pehle 12W tha).
Performancef ko track karta hai: ratio =1.6/2.0=0.8.
Perf/watt improvement=power ratioperf ratio=6.72/120.8=0.560.8=1.4286.
WHY sirf V2f dynamic ke liye move karta hai:Pdyn=αCV2f. Yahan α (activity) aur C (fixed silicon capacitance) DVFS ke under nahi badte — same gates same transistors par switch karte hain — toh woh "before" aur "after" mein identically appear karte hain aur ratio lete waqt cancel ho jaate hain. Sirf V aur f actually move karte hain, jo V2f chodta hai.
WHY static sirf V ke saath scale karta hai:Pstat=VIleak, aur Ileak yahan constant rakhe jaane par, static power V mein linear hai — V ka ek factor, squared nahi — toh yeh dynamic se kam aggressively shrink karta hai.
Answer: total power 6.72W; perf/watt ≈42.9% up sirf 20% kam speed ke liye. Note karo leakage pure-dynamic gain ko dilute karta hai (Ex. 2.2 ke 56% se compare karo jahan leakage ignore thi).
Recall Solution 4.2
Throughput check (cores × frequency): single = 1×3GHz=3.0; dual = 2×1.5GHz=3.0. Equal throughput. ✓
WHY αC phir cancel hota hai: har core same silicon design hai, toh α aur C saare cores mein aur dono options mein identical hain — woh comparison se bahar factor out ho jaate hain, har core ki dynamic power ∝V2f chodke.
Single-core dynamic (V=1.0, f=3): ∝1.02×3=3.0 (αC⋅V2f ki units mein).
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 ≈56.25% dynamic power par — multicore ki jeet, seedha V2 se. Do slow cores ek fast core ko beat karte hain kyunki har ek lower voltage par run karta hai.
V ke function ke roop mein total power set up karo.f=2V substitute karo:
P(V)=0.5⋅V2⋅(2V)+V⋅1.0=V3+V.5 W par cap: solve karo V3+V=5.
Try karo V=1.5: 3.375+1.5=4.875 (thoda under). Try karo V=1.52: 3.511+1.52=5.03. Toh V≈1.5157V — Vth se comfortably above, toh simple model yahan valid hai.
V∗≈1.5157V⇒f=2V≈3.031GHz.Perf/watt. Performance ∝f hai, aur stated one-op-per-tick assumption se f=3.031GHz correspond karta hai 3.031GFLOPS se; power cap par 5W hai:
5W3.031GFLOPS≈0.606GFLOPS/W.WHY matter karta hai: cube term V3 ceiling ke paas dominate karta hai — last MHz squeeze karna disproportionate power costa hai, exactly isliye phones throttle karte hain. Answer: f≈3.03GHz, perf/watt ≈0.61GFLOPS/W.
Recall Solution 5.2
WHAT hum optimise kar rahe hain: perf/watt =V3+V2V=V2+12 (ek V cancel karo).
WHY derivative tool: ek smooth function ka maximum dhundhne ke liye hum poochte hain kahan uska slope zero hai — yahi derivative dhundhti hai.
dVd(V2+12)=(V2+1)2−2⋅2V=(V2+1)2−4V.
Yeh V>0 ke liye negative hai aur sirf V=0 par zero: efficiency V2+12V badhne par monotonically decrease karti hai. Toh is simple model mein theoretical peak sabse kam possible voltage par baithta hai (V→0+, efficiency →2).
WHY real chips wahan nahi baithte — teen reasons:
Frequency mar jaati hai.f=2V→0, toh chip maximally efficient ban jaati hai lekin har second almost koi kaam nahi karti — woh kabhi deadline meet nahi kar sakti. Efficiency (ops/joule) aur usefulness (ops/second) opposite directions mein pull karte hain.
Model Vth ke neeche toot jaata hai. Jab V threshold voltage ke paas jaata hai, transistors subthreshold region mein jaate hain: f∝V nahi rehta (speed linearly se zyada tezi se collapse hoti hai) aur constant-Ileak assumption fail hoti hai — leakage exponentially badhti hai, toh Pstat per unit work shrink hone ki jagah explode karta hai. Yeh sundar 2/(V2+1) curve wahan simply valid nahi hai.
Leakage per second fixed overhead hai. Low f par kaam ko drag out karna chip ko zyada der tak powered rakhta hai, aur Pstat=VIleak har second energy drain karta rehta hai — toh ek point ke baad voltage giraana ek fixed kaam ke liye total energy badha sakta hai.
Conclusion: real design target karta hai ==sabse kam voltage jo performance deadline meet kare aur safely Vth se upar rahe== — ek constrained optimum, kabhi mathematical V→0 peak nahi.
Neeche ki figure is problem ke dono curves ek voltage axis par draw karti hai: teal curve perf/watt=2/(V2+1) hai (har jagah falling, Ex. 5.2 confirm karta hai), aur burnt-orange curve total powerV3+V hai (V badhne par explode hota hai). Plum dashed line Ex. 5.1 se 5W TDP cap mark karti hai, aur plum dot solution V∗≈1.52V, f≈3.03GHz hai. Left par grey shaded band sub-threshold danger zone mark karta hai (V<Vth) jahan simple model valid nahi hai — curves sirf uske right side par padho.
Recall Solution 5.3
Energy = power × time, nodes par sum karo.
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 bhi (1.5h<2h).
Yahan Q dono par jeetta hai — low-clock nodes (lower V, toh V2 savings) extra nodes ke cost se zyada pay karte hain.
Trade-off statement: wide-and-slow (lower voltage par zyada nodes) aksar narrow-and-fast ko energy par beat karta hai, aur yahan time par bhi kyunki 8 nodes kaam ko parallelize karte hain; sirf woh cost jo Q pay karta hai woh hai higher up-front hardware aur zyada total idle/static power (8 chips har ek VIleak leak karte hain jab bhi idle hon), jo reliability aur capital-cost dimension hai jo pure energy sum quietly hide kar deta hai. Toh: is kaam ke liye Q chuno, lekin agar node cost ya leakage-at-idle tumhare budget dominate kare, comparison flip ho sakta hai.