Does matching accuracy also match serving cost?
Accuracy-Matched Is Not Cost-Matched: Pricing INT4 Reasoning Deployments by Served GPU Time per Solved Problem
Not peer reviewed
Abstract and notes
An INT4 deployment of a reasoning model is a choice of quantizer, repair, export form and decoding control, usually made by accuracy, generated tokens or a fixed-length benchmark, none of which sees how a serving engine charges for length. We serve Qwen3-4B in vLLM on an RTX 4090 and price each configuration by its measured GPU time per solved problem. Under KV-cache-limited load, INT4's extra tokens consume 41–47% of its per-token saving over BF16, against 6% at batch 1, and forcing output lengths and shrinking the KV pool trace this excess to KV-capacity preemption. A repair's time cost changes sign with its serving form: a distillation adapter served unmerged costs more than its INT4 base at batch 1, while merged and requantized it costs less at both loads. Configurations that match BF16's accuracy span a 1.61-fold range of GPU time per solved problem, ParoQuant's own kernel included; pass@1 has no rank agreement with this cost, and a fixed-length benchmark picks a configuration 21.4% costlier than the best. A scheduler replay fitted under load predicts five configurations' relative cost at unprofiled loads on the same GPU within 5.2%, and since on harder workloads and a second model the two configurations cheapest on GSM8K are never both accuracy-matched, each workload is screened and priced on its own.
Source: Zenodo