Accelerator
GPU, TPU, NPU or other inference accelerator energy.
A proposed framework for measuring how much useful AI performance is obtained from the physical energy consumed to produce it.
AI systems are commonly evaluated using accuracy, task scores, latency, throughput and economic cost. These measurements are essential, but they do not directly describe how efficiently a system converts physical energy into useful computational results.
LowJoule proposes treating energy as an explicit experimental variable alongside model quality.
Let Q denote a task-specific quality function and E the measured energy required to execute the evaluated workload.
The numerator is deliberately task-dependent. Useful intelligence cannot be reduced to a single universal score without specifying what constitutes useful performance for the workload being studied.
UI/J is currently a proposed research framework, not an established SI unit or standardized industry benchmark. Comparisons are meaningful only when task definition, quality metric, workload and energy-measurement boundaries are controlled.
For many experiments, relative efficiency is more informative than an isolated absolute score. Let π₀ represent a baseline policy and π₁ an experimental policy.
A value greater than one indicates improved quality-normalized energy efficiency relative to the selected baseline under the same experimental protocol.
A system can trivially consume less energy by performing less useful work. Energy savings should therefore be evaluated subject to an explicit quality constraint.
The tolerance ε must be declared before interpreting an energy reduction as an efficiency improvement.
Energy measurements depend strongly on system boundaries. LowJoule experiments should therefore explicitly declare which components are included.
GPU, TPU, NPU or other inference accelerator energy.
Host-side computation and orchestration.
Memory access and data movement where measurable.
Whole-node power when physical instrumentation is available.
Network or interconnect costs when relevant to the experiment.
Facility overhead may be reported separately when reliable data is available.
Fix the dataset, prompts, task distribution and evaluation procedure.
Select an explicit metric Q appropriate to the task.
Record accelerator, CPU, memory, software stack and runtime configuration.
Execute the fixed-compute policy and record quality, latency and energy.
Repeat the same workload using the LowJoule policy.
Repeat measurements and publish variance, confidence intervals and measurement assumptions.
The long-term objective is an open LowJoule benchmark in which models and computational policies can be compared across explicit quality-energy Pareto frontiers.
Rather than declaring a single universally optimal system, the benchmark would expose the trade-off between quality and physical energy across policies, models and hardware configurations.
The objective is not simply to make AI consume less energy. The objective is to eliminate computation whose expected utility does not justify its physical cost.