Skip to content
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

[WIP][[V1][Metrics] Implement max_num_generation_tokens metrics #14055

Draft
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

markmc
Copy link
Contributor

@markmc markmc commented Feb 28, 2025

(WIP until #13774 merges)

Part of #10582

This metric tracks the maximum of num_generation_tokens across a set of identical requests under a parallel sampling parent.

It is the last remaining metric used by the example Grafana dashboard that makes sense in V1.

Add some additional tracking of child requests to ParentRequest in order to facilitate this.

The initial implementation went to great efforts to add parallel
sampling as a wrapper at the highest layer of abstraction possible.
This resulted in a lot of tricky code to post-process RequestOutputs
to aggregate them where necessary.

Instead, it probably makes sense to implement parallel sampling at
the layer that actually creates RequestOutput objects - i.e. in
OutputProcessor.

To do this, we simply need to allow for fanning out child requests
in LLMEngine.add_request(), passing details of the fan-out to
OutputProcessor.

This adds some overhead to the n=1 case (see SingularSamplingRequest)
in return for significantly less overhead and complication in the
parallel sampling case.

Signed-off-by: Mark McLoughlin <[email protected]>
Address PR feedback from Nick.

Signed-off-by: Mark McLoughlin <[email protected]>
Fixes:

TypeError: RequestOutput.__init__() missing 1 required positional argument: 'outputs'

Signed-off-by: Mark McLoughlin <[email protected]>
Keeping the output aggregator on RequestState was just a silly
refactoring mistake - it clearly needs to be on the parent
request since we are aggregating across child requests.

Also address some PR feedback from Nick to make the logic
here less confusing.

Signed-off-by: Mark McLoughlin <[email protected]>
Now that we're not returning a RequestOutput for all
finished requests, we need to perform finished request
handling even without a RequestOutput now.

Signed-off-by: Mark McLoughlin <[email protected]>
Based on excellent PR feedback from Nick.

Signed-off-by: Mark McLoughlin <[email protected]>
Move all the logic for child request output aggregating
into parallel_sampling.ParentReq.

Signed-off-by: Mark McLoughlin <[email protected]>
PR feedback from Andy.

Signed-off-by: Mark McLoughlin <[email protected]>
PR feedback from Andy.

Signed-off-by: Mark McLoughlin <[email protected]>
PR feedback from Andy.

Signed-off-by: Mark McLoughlin <[email protected]>
Not a perfect set of categories, but should make it easier to
navigate.

Signed-off-by: Mark McLoughlin <[email protected]>
This metric tracks the maximum of num_generation_tokens across
a set of identical requests under a parallel sampling parent.

It is the last remaining metric used by the example Grafana
dashboard that makes sense in V1.

Add some additional tracking of child requests to ParentRequest
in order to facilitate this.

Signed-off-by: Mark McLoughlin <[email protected]>
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

@markmc markmc changed the title [WIP[[V1][Metrics] Implement max_num_generation_tokens metrics [WIP][[V1][Metrics] Implement max_num_generation_tokens metrics Feb 28, 2025
@mergify mergify bot added the v1 label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant