mlsanityData to 13 Oct 2026

Beyond Per-Token Pricing: A Concurrency-Aware Methodology for LLM Infrastructure Cost Estimation

arXiv 2606.11690 ↗First posted 10 Jun 2026cs.DC cs.PFcited by 2

Not on the map. Why?

Abstract (arXiv)

Every public LLM cost calculator we surveyed treats GPU utilization as a fixed input -- entered by the user, baked in as a preset, or silently assumed at 100% -- never measured against the operator's actual load. We show that this assumption is the dominant source of error: on identical H100 hardware, effective cost spans 0.21 to 15.25 per million output tokens, an underutilization penalty of 2.5-24x across low-to-moderate enterprise loads (1-10 rps) and up to 36.3x near idle -- driven by one operator-controlled variable, offered request rate lambda, which sets in-flight concurrency via Little's Law and which no open-source calculator exposes. Because calculators take utilization as a user-supplied input, any utilization-naive estimate understates true cost by exactly 1/U, systematically mispricing self-hosting -- most severely over-selling it for low-traffic workloads. We propose a measurement methodology that parameterizes the relationship as Ceff = f(H, M, Q, lambda, L), validate it with 42 benchmarks across dense, ultra-sparse MoE, and sparse MoE models, and release vllm-cost-meter, an open-source cost meter that attaches to a live vLLM server and reports real /M-tokens against the operator's own traffic. We further show that FP8 quantization benefits the MoE architectures we tested roughly 2.2-2.4x more than the dense model (+69 to +74% vs. +31% peak throughput; n=3, broader validation needed), and our data are consistent with active parameter count, not total model size, being a primary predictor of saturation economics. To rule out single-hardware confounding we repeat the core sweep on A100 80GB PCIe (56 runs): the load-driven spread reproduces at 7.0-11.4x, the active-parameters ordering survives at FP8, and the dense-FP8 advantage inverts on silicon without native FP8 tensor cores -- a hardware-conditional caveat the framework already accommodates.

Key facts. Cited by 2 papers in the map (data through 13 Oct 2026). First posted on arXiv 10 Jun 2026.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 13 Oct)

Citing papers per year: 2026: 2.

2 papers.

Similar, not cited

Close in wording, no citation either way

  1. 2026Token-Budget-Aware Pool Routing for Cost-Efficient LLM Inference
  2. 2026Position: LLM Inference Should Be Evaluated as Energy-to-Token Production
  3. 2026Cost-Aware Speculative Execution for LLM-Agent Workflows: An Integrated Five-Dimension Method
  4. 2026Request-Level Energy Attribution for Batched LLM Serving
  5. 2026Cost-Governed RAG: Unified Per-Tenant Cost Attribution Across Retrieval and Generation in Multi-Tenant LLM Systems
  6. 2026Efficiency and Cost Alignment in Batched LLM Serving via Resource-Fair Scheduling
  7. 2026Dual-Pool Token-Budget Routing for Cost-Efficient and Reliable LLM Serving
  8. 2026Characterization of Request and Token Energy Costs for LLM Inference Workloads on GPU Platforms