Repository navigation
AgentX: report E2E Output Token Throughput (avg/P50/P90/P99) as the headline metric - #5571
Open
dwadhwaniTT wants to merge 2 commits into
Open
dwadhwaniTT wants to merge 2 commits into
dwadhwaniTT wants to merge 2 commits into
Conversation
Export avg/P50/P90/P99 of AIPerf's e2e_output_token_throughput as mean/median/p90/p99_speed_tps and render them as the first table of the agentic-traces report. This is the metric Artificial Analysis (avg) and OpenRouter (P50) publish. P90/P99 use the worse-tail convention, so they read AIPerf's p10/p1. The duplicate "E2E Norm Intvty" columns are dropped from the throughput table; the e2e_norm_intvty fields stay in the payload and agenticSweep export, so requirements grading is unchanged. Closes #5570 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dwadhwaniTT
marked this pull request as ready for review
November 13, 2026 19:49
dwadhwaniTT
requested review from
a team,
ddjukicTT,
fivanovicTT,
idjuricTT and
vpetrovicTT
as code owners
November 13, 2026 19:49
bgoelTT
requested changes
Nov 13, 2026
bgoelTT
left a comment
Collaborator
There was a problem hiding this comment.
Changes look great, but can you please preserve the aiperf official terminology of "E2E Output Token Throughput"?
Rename the speed fields to mean/median/p90/p99_e2e_output_token_throughput and label the report table, columns, definition and log line with AIPerf's official term. "speed" remains only where the text maps the metric to what Artificial Analysis publishes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #5570
Summary
Makes AIPerf's E2E Output Token Throughput the headline metric of AgentX reports, under AIPerf's own name. It is output tokens divided by total request time, with TTFT included, and it is the number Artificial Analysis ("speed", average) and OpenRouter ("throughput", P50) publish for a deployment.
llm_module/drivers/aiperf_agentic_traces.py): exportsmean_e2e_output_token_throughput,median_e2e_output_token_throughput,p90_e2e_output_token_throughputandp99_e2e_output_token_throughputfrom AIPerf'se2e_output_token_throughput. P90/P99 use the worse-tail convention that OpenRouter now uses (P99 is the rate only 1% of requests fell below), so they read AIPerf'sp10/p1. The end-of-run log prints all four.report_module/agentic_traces_renderer.py): a new "Per-run E2E Output Token Throughput (tok/s per request)" table is the first metric table, with Avg (AA), P50 (OR), P90 and P99 columns. A definition explains the metric. The "E2E Norm Intvty" columns, which showed the same values, are removed from the throughput table.e2e_norm_intvtyfields stay in the payload and in theagenticSweepexport, so grading against requirements documents is unaffected. swo-bench rows have no such metric, so the table does not appear for them.docs/workflow_development.mddocuments the fields. New tests cover the parser mapping and the table's position, columns and formatting.Testing
profile_export.jsonlgives exactly the same values.launchers/run_agentic_traces.py(Kimi-K2.7 config, CI mode, 8 concurrent users, 900 s) against a local OpenAI-compatible stand-in for vLLM, not real hardware. The run passed acceptance. The report's E2E Output Token Throughput table showed 45.62 / 46.55 / 36.59 / 12.85, which matches the per-request recomputation over 339 requests.agentic_sweep.jsonstill carries thee2eNormIntvty*fields.🤖 Generated with Claude Code