Glossary › Test-Time Compute
Test-Time Compute
Spending more inference compute on a single request to get a better answer: longer reasoning, sampling several answers and voting, or searching over candidate solutions. A dial that trades latency and cost for accuracy, with diminishing returns.
Where Test-Time Compute shows up
All matching postsReasoning Models, Post-Training, and Test-Time Compute
Where reasoning models come from, what they cost, and when to pay for them. The SFT to DPO to GRPO pipeline, reinforcement learning with verifiable rewards, test-time compute as a dial, and a method for deciding which of your requests deserve a thinking model.
Reasoning Models and Test-Time Compute: When to Pay for Thinking
Reasoning models trade tokens for accuracy, and every request is a decision about whether that trade is worth it. Here is what test-time compute is, why its returns diminish, a four-setting method to find the knee for your workload, and the routing rule that keeps the bill sane.