OPEN SOURCE · FLAGSHIP · APACHE 2.0

energy-per-result

One unit for every energy claim: joules per correct result, with the meter boundary stated.

0.35 J
per correct result · Apple M1
14.8 J
per correct result · RTX 4090
10/10
correct runs on both backends
Monthly
tagged releases with evidence

Why it exists

Vendors publish energy advantages measured on their own terms: different workloads, different system boundaries, cooling in or out. Those claims cannot be compared. This benchmark fixes the task, states the meter boundary and counts only correct answers, so wrong runs make the number worse, exactly as they should.

The pipeline

epr CLI Task registry Apple M1 RTX 4090 QPU Correctness |E − E₀| < 1.6 mHa Aggregator median J / correct Evidence logs · screenshots Zenodo DOI per release one command H₂ VQE · target fixed meter boundary, stated powermetrics NVML, board next backend

Every release is tagged, every run keeps its evidence in the repo under docs/evidence.

First results

The first task is the H2 ground state via VQE, solved to chemical accuracy. On this workload the MacBook beats the datacentre GPU by roughly forty times, because a two qubit simulation cannot fill a 450 watt board. The interesting question the benchmark now makes answerable is where the crossover sits as circuits grow.

Roadmap: a real QPU through a cloud provider, then an AMD Kria class edge board as a permanent lab fixture. One backend per month, each a tagged release.