Lead Green
A Katonic project

Compare · Two precisions · H100 and B200

Qwen 3 235B A22B Instruct FP8 vs Qwen 3 235B A22B Instruct: GPU energy per million output tokens

On the index rows, Qwen 3 235B A22B Instruct uses 1.47× the GPU energy per output token of Qwen 3 235B A22B Instruct FP8 on the H100 (303.5 against 206.0 Wh/M, both on eight cards at running batches of 228 and 511) and 0.48× on the B200 (66.7 against 139.1 Wh/M, on four cards and two cards at running batches of 3,765 and 256), GPU only, each at the most energy-efficient configuration the ML.ENERGY Leaderboard v3.0 measured for it (data compiled 16 February 2026). Qwen 3 235B A22B Instruct FP8 has 235 B parameters, 22 B active per token; Qwen 3 235B A22B Instruct has 235 B parameters, 22 B active per token. Part of each gap is the sweep rather than the model: the two rows of a pair differ in card count and running batch, and the table states both.

Unit watt-hours per million output tokens (Wh/M). GPU only, busy server. Every row is a floor. Data qwen-3-235b-a22b-instruct-fp8.json, qwen-3-235b-a22b-instruct.json. Updated 19 October 2026.

Cite this page: Lead Green, a Katonic project. Qwen 3 235B A22B Instruct FP8 vs Qwen 3 235B A22B Instruct: GPU energy per million output tokens. https://leadgreen.ai/compare/qwen-3-235b-a22b-instruct-fp8-vs-qwen-3-235b-a22b-instruct/, release 2026-10-19, retrieved [date]. CC BY 4.0.

H100, index rows1.47×Qwen 3 235B A22B Instruct 303.5 Wh/M on 8 × H100 against Qwen 3 235B A22B Instruct FP8 206.0 Wh/M on 8 × H100.
B200, index rows0.48×Qwen 3 235B A22B Instruct 66.7 Wh/M on 4 × B200 against Qwen 3 235B A22B Instruct FP8 139.1 Wh/M on 2 × B200.
Parameters1.0×Qwen 3 235B A22B Instruct 235 B parameters, 22 B active per token; Qwen 3 235B A22B Instruct FP8 235 B parameters, 22 B active per token.

Each ratio compares the two models' index rows on the same GPU: the lowest-energy configuration the leaderboard measured for each, at or under 500 ms median inter-token latency. The ratio is the second model's energy per token over the first's, so a figure under 1 means the second model's row is the lower one. Card count and running batch differ between the rows and are shown in the table.

The rows

Index rows on every GPU both models share

Index rows for Qwen 3 235B A22B Instruct FP8 and Qwen 3 235B A22B Instruct, with the configuration behind each and the per-answer and carbon readings
GPUModelCardsPrecisionRunning batchGPU WTokens / sWh / MOutput tokensWh per answerkg CO2e / bn tokens, world grid
H100Qwen 3 235B A22B Instruct FP88 × H100FP85113,9615,342206.08810.18297.4
H100Qwen 3 235B A22B Instruct8 × H100BF162284,0383,696303.58740.265143.6
B200Qwen 3 235B A22B Instruct FP82 × B200FP82561,8913,776139.18760.12265.8
B200Qwen 3 235B A22B Instruct4 × B200BF163,7653,19613,30366.78740.05831.6

Running batch is the average number of requests the server was decoding at once over the steady-state window (vLLM's num_requests_running). GPU W is the measured average power summed across the cards. Wh per answer is Wh/M times the row's own average output length. Carbon uses the world average grid, 473 gCO2e per kWh (Ember, 2024); the grid pages price every model on each listed grid. Model names link to every measured configuration.

What explains it

Two precisions

The same model weights at two precisions. FP8 stores each weight in one byte and BF16 in two, so an FP8 row moves half the bytes per token from memory and the model fits on fewer cards or leaves more memory for batching. The FP8 row uses less energy per token on the H100 and more on the B200 (H100: FP8 206.0 Wh/M on eight cards at a running batch of 511, BF16 303.5 Wh/M on eight cards at 228; B200: FP8 139.1 Wh/M on two cards at a running batch of 256, BF16 66.7 Wh/M on four cards at 3,765). Where the FP8 row costs more, the reason is in the table: the two rows were swept to different card counts and reached different running batches, and a quieter row carries a higher energy per token whatever its precision. Quantisation is the cheapest energy lever after load, but these rows show it only pays when the serving configuration is matched; the model pages hold every configuration so the pair can be re-cut at the same cards and cap.

Load still moves the number more than either model does: Qwen 3 32B on 2 × H100 spans 7.1× between a running batch of 8 and 256 on the same cards, which is wider than the gap on this page. Pick the model for the task, then run it busy. The running batch and floor entries define the terms.

Questions

Asked about Qwen 3 235B A22B Instruct FP8 against Qwen 3 235B A22B Instruct

Is Qwen 3 235B A22B Instruct FP8 more energy-efficient than Qwen 3 235B A22B Instruct?

It depends on the GPU: on the ML.ENERGY Leaderboard's index rows, Qwen 3 235B A22B Instruct uses 1.47× the GPU energy per output token of Qwen 3 235B A22B Instruct FP8 on the H100 (303.5 against 206.0 Wh per million output tokens) and 0.48× the GPU energy per output token of Qwen 3 235B A22B Instruct FP8 on the B200 (66.7 against 139.1 Wh per million output tokens). These are floors at high load, GPU only, and the two rows of a pair differ in card count and running batch.

How much more energy does Qwen 3 235B A22B Instruct use per million tokens than Qwen 3 235B A22B Instruct FP8?

The index rows differ by 97.6 Wh/M on the H100 (97.6 kWh per billion tokens) and 72.3 Wh/M on the B200 (72.3 kWh per billion tokens); where the ratio is under 1, Qwen 3 235B A22B Instruct is the lower row. Per answer, at each row's own average output length, Qwen 3 235B A22B Instruct FP8 costs 0.182 Wh on the H100 and 0.122 Wh on the B200 and Qwen 3 235B A22B Instruct 0.265 Wh on the H100 and 0.058 Wh on the B200.

Does FP8 save energy compared with BF16 for the same model?

Not consistently on these index rows. On the H100 the FP8 row (Qwen 3 235B A22B Instruct FP8) uses 206.0 Wh/M on 8 cards at a running batch of 511 and the BF16 row 303.5 Wh/M on 8 at 228; on the B200 the FP8 row (Qwen 3 235B A22B Instruct FP8) uses 139.1 Wh/M on 2 cards at a running batch of 256 and the BF16 row 66.7 Wh/M on 4 at 3,765. FP8 halves the bytes moved per token and the memory the weights take, but the leaderboard swept the two variants to different card counts and loads, and load moves energy per token more than precision does. A matched run, same cards and same cap, is the comparison to ask a vendor for.

Why are the two rows not like for like?

The leaderboard sweeps each model separately: card count, the cap on requests in flight and the precision are chosen per model, and the running batch actually reached differs. On the H100 the rows here ran on 8 and 8 cards at running batches of 511 and 228. The ratio compares the best measured row on each side, not a matched run; every configuration is on the model pages and in the API, so any pair can be re-cut at a matched cap or running batch.

Where do these figures come from?

The ML.ENERGY Leaderboard v3.0 (data compiled 16 February 2026, retrieved 26 September 2026), Text Conversation task, GPU energy measured with Zeus under vLLM on H100 80GB HBM3 and B200 servers; each row is the lowest-energy configuration for its model and GPU at or under 500 ms median inter-token latency. Carbon per billion tokens multiplies the row by the world average grid intensity, 473 gCO2e per kWh (Ember, 2024).

Sources

Where every figure came from

ML.ENERGY Leaderboard version 3.0 (released 1 December 2025; data compiled 16 February 2026; retrieved 26 September 2026), The ML.ENERGY Initiative, started at SymbioticLab, University of Michigan. Text Conversation task, 328 stable configurations. Energy per token is steady-state GPU energy divided by the output tokens generated in the window, measured with Zeus under vLLM 0.11.1 on H100 80GB HBM3 and B200 servers; energy per request is that figure times the average output length. Each index row is the lowest-energy configuration for its model and GPU at or under a 500 ms median inter-token latency, the leaderboard's own default ceiling, which no configuration reaches. Apache 2.0 per the ml-energy/benchmark-v3 dataset card. Cite Chung et al., The ML.ENERGY Benchmark, NeurIPS 2025 Datasets and Benchmarks.

Parameters and architecture as the leaderboard records them (total and activated parameters in billions). Carbon: Ember, Yearly electricity data, October 2026 release, world average 2024, CC BY 4.0, retrieved 17 October 2026.

Cite as. Lead Green, a Katonic project. Green Tokens: GPU energy per million output tokens. https://leadgreen.ai/index/, release 2026-10-19, retrieved [date]. © 2026 Katonic AI Technology Ltd. Licensed CC BY 4.0, offered as-is and without warranty; state whether you changed any rows or columns. Underlying data: ML.ENERGY Leaderboard v3.0 (The ML.ENERGY Initiative; Apache 2.0 per the ml-energy/benchmark-v3 dataset card; cite Chung et al., The ML.ENERGY Benchmark, NeurIPS 2025 Datasets and Benchmarks, arXiv 2505.06371); Ember, Yearly electricity data, October 2026 release (CC BY 4.0); AI Energy Score (Apache-2.0 as tagged on its Space; results reproduced as facts with attribution); NVIDIA figures reproduced as facts from the documents named in the sources ledger.