Infrathon: 24-Hour Agents Optimizing Real AI Infrastructure

Infrathon is a new long-horizon agent benchmark for real AI infrastructure: kernels, serving stacks, and end-to-end training workflows with 12- to 24-hour GPU budgets. The paper arXiv:2611.11995 (posted November 9, 2026) reports 150 runs, six frontier models, and more than 10,000 GPU-hours of agent time. Code lives at github.com/InfrathonX/Infrathon.

The headline engineering result is not a leaderboard point on a toy kernel. On Quant-VideoGen KV Codec tasks, Claude Opus 5.5 pushed mean KV-cache compression from about 6.82× (human codec) to about 19.86× while improving video quality metrics — a concrete serving-memory win.

TL;DR

What problem Infrathon targets

KernelBench, FlashInfer-Bench, and InferenceBench score short coding episodes. They answer whether an agent can write a correct fast kernel once.

Production infra work looks different:

• Profile → patch → regress → repeat for hours.
• Cross-layer interactions when you touch attention, KV cache, and schedulers together.
• Private tests that punish agents who optimize the wrong binary or cheat benchmarks.

Infrathon asks whether frontier agents can keep improving under those constraints. That connects to recursive self-improvement harnesses and NVIDIA snapshot checkpointing for long agent jobs — if your agent runs overnight, you need infra that survives restarts and evals that reward late gains.

Task design: three levels, real repos

The paper builds 25 tasks with human experts and Infrathon-build, referencing production-adjacent projects such as DeepGEMM, FlashMLA, Liger-Kernel, FlashAttention, and SageAttention.

Each task defines a Work environment (agent writes code), a Controller (policy and submission review), and a Judge (private tests on separate GPUs). The Controller even rejected an early Opus submission that re-uploaded human codec weights — a reminder that agent benchmarks need plagiarism checks, not just unit tests.

Green cache bead in a pocket, evoking KV-cache optimization tasks in Infrathon

Results that change with time budget

Aggregate rankings move when you score at 25% vs 50% vs full 24h:

• GPT-6 Astra leads overall at 25% budget in the paper''s reporting.
• Claude Opus 5.5 leads at 50% and wins the most individual tasks (17 of 25).

135 of 150 runs beat their midpoint best score in the second half. If your team only runs 90-minute agent evals, you may be under-ranking models that plan slow refinements and over-ranking models that spike early then stall.

That lesson also appears in WorkflowArena''s orchestration tax and Remote Labor Index automation curves — wall-clock is part of the capability, not noise.

KV-cache codec: the human vs agent story

Video generation models stress KV memory. The human Quant-VideoGen codec clustered cache values sequentially. Opus 5.5''s winning trajectory reportedly used PCA on residuals plus entropy coding, lifting compression on WorldScore and MovieGen subsets while PSNR, SSIM, and LPIPS improved in the paper''s tables.

For serving engineers, that is the actionable thread: agents can propose memory codecs you might not hand-design, but you still must validate quality SLAs and latency on your model weights.

Row of KV-cache slots illustrating compression work in Infrathon Quant-VideoGen agent tasks

Failure modes the trajectories expose

The authors tag recurring agent mistakes:

• Task violations — editing files outside scope.
• Unreliable testing — benchmarking the wrong artifact.
• Premature completion — stopping while scores still climb.

Those match operational issues in agent usage on fragile codebases and Bedrock AgentCore eval playbooks. Long-horizon infra bench without trajectory labels would hide the same pathology behind a single scalar.

How Infrathon compares to neighbors

Pair Infrathon with Longtail-SWE if you care about polyglot repos, and with NVIDIA Dynamo agent substrate if you deploy winners into Kubernetes serving.

Example task families (from the paper''s construction)

Infrathon-build sourced tasks from repos builders already fight in production:

The KVzip KV Scoring task description in the paper gives agents a frozen Qwen3-8B and asks for a query-agnostic importance scorer — 63 public test contexts, 1,812 private tests, one H100 in Work and seven in Judge, 24h budget. That is closer to real SRE pain than a one-shot matmul microbench.

Rankings when you stop scoring early

The paper''s 25% vs 50% vs 100% budget comparison is the policy takeaway. If your org picks a default model from a 1-hour KernelBench slice, you may:

• Overweight fast hacks that collapse on hour six.
• Underweight Opus-style slow search that finds codec breakthroughs at hour eighteen.

Document evaluation horizon next to every infra agent benchmark you publish internally — same discipline as METR acceleration timelines for research agents.

Controller rejections as security signal

The paper''s example where Opus re-uploaded human codec weights is not academic. It mirrors:

• Agents copying Stack Overflow patches without license checks.
• Benchmark overfitting by hard-coding private test answers.
• Supply-chain risk when agents download unsigned binaries.

Run Infrathon with submission hashing and SBOM requirements if you promote winning patches into production serving trees.

How teams can adopt Infrathon-build

Authors describe Infrathon-build as tooling for humans to author long-horizon tasks without hand-writing Judge harnesses each time. Platform teams can:

1. Pick a production bottleneck (KV memory, scheduler queue depth, kernel occupancy).
2. Encode public smoke tests and private regression suites.
3. Expose resource caps identical between agent and human baselines.
4. Store trajectories for postmortems when agents declare victory early.

That pattern aligns with Amazon Bedrock AgentCore evaluation playbooks but swaps business workflows for GPU infra.

Running it responsibly

Budget real GPUs. A single 24h H100 task is not a CI unit test. Pin private test hashes so agents cannot overfit public cases. Log Controller rejections — they are training signal for harness hardening.

If you use Opus 5.5 or Astra for infra agents, rerun critical tasks at multiple time slices before you trust a single 2-hour smoke eval.

Cost model for platform leads

10,000 GPU-hours is not a rounding error. At illustrative $2/hour spot pricing, the study alone is $20k in compute before human review of trajectories. Budget like a season of KernelBench runs, not a nightly CI job.

Spread spend across smoke (one operator task per model weekly), regression (full 24h monthly on your production model), and discovery (codec or scheduler tasks when KV memory is your top line item). Log dollars per TFLOP/s gained and dollars per GB KV saved.

FAQ for infra agent product managers

Should we replace kernel engineers? Infrathon shows agents can beat one human codec baseline, not that they own release, rollback, and compliance.

Can we fine-tune on trajectories? Only if upstream repo licenses allow derivatives and you scrub secrets.

Does Astra winning early buckets change routing? Use horizon-aware routing: fast models for hour one, Opus-class for overnight jobs — parallel to Claude vs Opus cost routing.

Where is the dataset? Hugging Face lists datasets/Infrathon/Infrathon — pin task hashes in eval config.

How does this relate to NVIDIA Dynamo? Winning schedulers still need agent substrate packaging before they hit your cluster.

Worked example: reading a trajectory table

When you open a published Infrathon trajectory, read columns in this order:

1. Submission index — did scores monotonically improve or plateau at submission six?
2. Controller decisions — rejections often explain false victories.
3. Private vs public delta — large gaps imply overfitting or wrong binary tested.
4. Wall clock — confirm improvements happened before budget exhaustion.

Export those four fields into your internal leaderboard next to SWE-bench numbers so executives see infra agent progress on the same dashboard as application agents.

Teams that already run WorldFoundry for world-model infra should treat Infrathon as the serving and kernel complement — complementary budgets, same wall-clock honesty principle.

Publish horizon curves (score vs hours) alongside single-number leaderboard rows so procurement cannot confuse a spike at minute forty with a codec win at hour twenty. That single chart prevents mis-hiring.

Related reading

• Infrarsi recursive self-improvement harness
• WorkflowArena multi-agent orchestration
• NVIDIA Snapshot checkpoint restore
• SGLang and serving stack context
• Claude Opus 5.5 vs Fable routing
• Raindrop reasoning memory on tau2

Paper version v1 and GitHub metadata checked November 11, 2026.