Skip to content

Revamp Agentic Inference benchmark guide - #431

Merged
hvagadia merged 3 commits into
mlcommons:mainfrom
hvagadia:agent/agentic-inference-submission-guide
Jul 29, 2026
Merged

Revamp Agentic Inference benchmark guide#431
hvagadia merged 3 commits into
mlcommons:mainfrom
hvagadia:agent/agentic-inference-submission-guide

Conversation

@hvagadia

Copy link
Copy Markdown
Collaborator

Summary

  • reorganize the Agentic Inference README around supported models, server setup, client configuration, and benchmark execution
  • document official submission requirements for sampling, thinking preservation, dataset replay, salting, inter-turn delays, tail handling, and accuracy
  • add the model-specific inline, OSL, and SWE-bench accuracy thresholds
  • align the Kimi and Qwen example YAMLs with the 613-trajectory dataset and make required replay settings explicit

Why

Submitters need a single, model-aware guide that distinguishes configurable deployment choices from the settings required for official Agentic Inference submissions.

Validation

  • uv run pre-commit run --all-files
  • loaded both example YAMLs through BenchmarkConfig.from_yaml_file
  • verified the commit contains only the README and two example YAML files

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@github-actions

Copy link
Copy Markdown

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

@hvagadia
hvagadia marked this pull request as ready for review July 29, 2026 19:12
@hvagadia
hvagadia requested a review from a team July 29, 2026 19:12
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@920ef49). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #431   +/-   ##
=======================================
  Coverage        ?   81.58%           
=======================================
  Files           ?      143           
  Lines           ?    19163           
  Branches        ?        0           
=======================================
  Hits            ?    15635           
  Misses          ?     3528           
  Partials        ?        0           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread examples/10_Agentic_Inference/README.md Outdated
Comment thread examples/10_Agentic_Inference/README.md Outdated
Comment thread examples/10_Agentic_Inference/README.md
@hvagadia
hvagadia merged commit 111cf76 into mlcommons:main Jul 29, 2026
8 checks passed
Comment on lines -171 to +99
Agentic inference benchmarks can have a long tail because different users receive
trajectories with very different turn counts, delays, and generated lengths. In
large runs this tail can last up to an hour after steady-state work has already
ended, so the benchmark separates the performance window from the remaining
accuracy/logging drain.
Agentic inference benchmarks can have a long tail because different users receive trajectories with very different turn counts, delays, and generated lengths. In large runs this tail can last up to an hour after steady-state work has already ended, so the benchmark separates the performance window from the remaining accuracy/logging drain.

The benchmark stops performance tracking when the first active user finishes its
final assigned trajectory. It emits `STOP_PERFORMANCE_TRACKING` at that point to
avoid measuring the tail. Turns issued before this event remain in the
performance window even if they finish later; turns issued after it are excluded
from performance metrics.
The benchmark stops performance tracking when the first active user finishes its final assigned trajectory. It emits `STOP_PERFORMANCE_TRACKING` at that point to avoid measuring the tail. Turns issued before this event remain in the performance window even if they finish later; turns issued after it are excluded from performance metrics.

For final submissions, keep
`agentic_inference.stop_issuing_on_first_user_complete: false` so the client finishes
already-started trajectories for accuracy. During optimization, set it to `true`
to stop issuing future turns at the performance boundary and shorten the tail.
For official submissions, submitters must set `agentic_inference.stop_issuing_on_first_user_complete` to `false` so the client finishes already-started trajectories for accuracy. During optimization, set it to `true` to stop issuing future turns at the performance boundary and shorten the tail.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These don't seem like real diffs - only formatting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants