Repository navigation
[Test][MiniCPM-o] Gate the duplex server-side TTFT/TTFP anchor in e2e; restore plugin policy tests #7872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
chickeyton
wants to merge
6
commits into
vllm-project:main
Choose a base branch
from
chickeyton:duplex_restore_tests
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[Test][MiniCPM-o] Gate the duplex server-side TTFT/TTFP anchor in e2e; restore plugin policy tests #7872
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
10ffb1a
[Bugfix][MiniCPM-o] Restore the duplex server-side response timing lo…
chickeyton a1812d8
Merge branch 'main' into duplex_restore_tests
chickeyton bf20832
Merge branch 'main' into duplex_restore_tests
chickeyton e3f0acf
Merge branch 'main' into duplex_restore_tests
chickeyton 770adc2
Merge branch 'main' into duplex_restore_tests
chickeyton bca8440
Merge branch 'main' into duplex_restore_tests
chickeyton File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] This hunk rewrites duplex Chat-audio metadata (
format/sample_rate_hz/ `m…Evidence and suggested fix
This hunk rewrites duplex Chat-audio metadata (
format/sample_rate_hz/metadata.audio_duration_ms) while the same PR restoresresponse_request_metricsonresponse.createdand every audio delta, but two in-page contracts still describe the old client-only story. L270 saystiming_summaryreports client-observed first-text / first-audio latency; L438's Tier 2response.output_audio.deltarow lists only format/sample_rate/duration/playback. The page never namesresponse_request_metrics. Unchanged by this diff,EventCollector.timing_summaryalready prefers serverttft_ms/ttfp_ms(source: server_request_start_and_client_receive) — the Omni-DuplexEval criterion this restore is for. Update those two passages to name the field.Evidence: Trigger: this PR attaches
response_request_metricson the duplex wire (vllm_omni/engine/duplex/session/model_channel.py:790created_payload["response_request_metrics"] = dict(response_request_metrics)and the same dict on audio-deltametadata.vllm_omni) and rewrites this page's Chat-audio section (docs/serving/realtime_duplex_api.md:504On the duplex route the audio delta itself carries the output \format` and). Adverse effect / unmet requirement: a reader of the same public page is still told the client-only contract, so they will misread Omni-DuplexEval TTFT/TTFP as receive-clock numbers. Unchanged by this diff, present in the PR-time tree:docs/serving/realtime_duplex_api.md:270``timing_summaryreports client-observed first-text / first-audio latency, ``;docs/serving/realtime_duplex_api.md:438``response.output_audio.delta|format,sample_rate_hz,metadata{session_id, epoch, model_speak, end_of_turn, audio_duration_ms, audio_text_marks, playback}`` (file has zeroresponse_request_metricsmentions). Unchanged by this diff, present in the PR-time tree:vllm_omni/clients/duplex.py:1753-1756"server_request_start_and_client_receive" if server_ttft_ms is not None or server_ttfp_ms is not None else "client_monotonic_receive"and:1760-1761server_ttft_ms if server_ttft_ms is not None else (...client receive...);vllm_omni/benchmarks/duplex_session_metrics.py:69Per-response TTFT/TTFP prefer server ``response_request_metrics```.Suggestion:
timing_summaryprefers per-response TTFT/TTFP from serverresponse_request_metricswhenresponse.createdor an audio delta carries them (source: server_request_start_and_client_receive); otherwise it falls back to client-observed first-text / first-audio latency.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. The doc now says server timing is preferred and lists
response_request_metricsin the event table.