benchmarks evals
A Prompt Optimizer Learned How Much Evidence It Could Afford
BudgetAPO sized evaluation slices to task noise and kept every comparison paired under strict call limits.
Summary
BudgetAPO sized evaluation slices to task noise and kept every comparison paired under strict call limits.
Automatic prompt optimizers often assume hundreds or thousands of model calls, a poor fit for paid or rate-limited systems. BudgetAPO begins with a short noise probe, sizes each evaluation slice to the task, and compares candidates on a fixed paired slice. Across seven benchmarks and five subject models, the authors report that it ranked first for every subject under their tests. At a 250-call budget it returned the unchanged seed prompt in 13% of runs, versus 86% for GEPA; on GPT-OSS-20B, GEPA needed 4.5 times as many calls to match BudgetAPO's 100-call score. The result turns budget allocation into part of the optimizer rather than an external limit it discovers too late.
Why it matters
BudgetAPO sized evaluation slices to task noise and kept every comparison paired under strict call limits.
Limits and context
No additional limitation was separately recorded.
Key claims
BudgetAPO sized evaluation slices to task noise and kept every comparison paired under strict call limits.
Evidence: source-2026-10-06-006
Sources
- arXiv preprint 2610.05671arXiv · primary research
Corrections
No corrections have been recorded for this story.