01The Win
The smaller task is a real achievement.
Google attributes its reported improvement to work across models, hardware and serving systems. Reducing the resources needed to deliver an answer is meaningful engineering progress.[1]
02The Tradeoff
The number of tasks does not stand still.
The IEA points to growing use and more demanding applications, including video, reasoning and agents. Efficiency is one part of a changing system.[2]
03What We Learned
Always ask: less per what?
A claim about one task and a claim about the whole system answer different questions. Before comparing them, check the task, time period and measurement boundary.
04What We Can Do
Keep two measures in view.
When evaluating an AI workflow, ask for resources per useful result and total resources over time. Define the result first. A smaller number means more when we know what it describes.