You Never Know
Grad-school work on worst-case execution time — and how the same method jumped to energy, then got dwarfed by scale. You never know. A look back — long before any of the tools we argue about now. The topic I was handed as a small first-year master's student in the late 1990s was WCET — Worst Case Execution Time — analysis. Wikipedia dates the term to around 2008, but I'd inherited the project…
After completing my master's degree on Worst Case Execution Time (WCET) analysis, I worked on improving the prediction methods, which became useful for energy consumption reduction and scaling. I built an abstract machine layer and spent time comparing systems, tackling challenges related to complex CPUs and cross-compiling. The concept of energy consumption became increasingly important as technology advanced and shifted towards mobile and embedded systems.
The parallelism and growth in computational power led to exponential growth, with issues related to scaling becoming less relevant. Looking back ten years from now, it is impossible to predict what the future holds.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
