Global temperature anomalies. Source: [1]
Sustainability ≠ Efficiency ≠ Performance
The concept of sustainability goes back to Hans Carl von Carlowitz (1645–1714), who wrote about forestry: do not harvest more timber than the forest can regenerate.[2] The standard framing uses three pillars: environment, society, economy. The lecture is clear that the environmental pillar is load-bearing. Without it, the other two collapse.
In computer science, performance, efficiency, and sustainability tend to get conflated. Rabl insists on keeping them apart:
- Efficiency: resources needed per task.
- Performance: how fast or how much work per unit time.
The car analogy makes the point concrete. Transport 200kg of cargo over a certain distance. A truck does it in one trip at 80km/h. A supercar can only carry 100kg, so it needs three trips (out, back, out). Even at 240km/h it merely ties the truck; it would need 417km/h to beat it on time - and it burns far more fuel regardless.[3] In systems research, we routinely scale the workload to the hardware and call the result "efficient." In real life, the task is fixed, and the mismatch matters.
The Hardware Wall
For decades, Moore's Law[4] and Dennard scaling[5] delivered exponential performance gains essentially for free: more transistors, constant power density, rising clock speeds. That ended in the mid-2000s. Frequency plateaued. The industry pivoted to parallelism, but horizontal scaling means more consumed power, and only a fraction of the chip can be fully active at once.[6]