Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Amitjoiya
Copy link

@Amitjoiya Amitjoiya commented Nov 15, 2025

… (#24684)

Purpose

Test Plan

Test Result


Essential Elements of an Effective PR Description Checklist
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

@github-actions
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 ask your reviewers to trigger select CI tests on top of fastcheck CI.

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.

If you have any questions, please reach out to us on Slack at https://slack.vllm.ai.

🚀

@mergify mergify bot added the performance Performance-related issues label Nov 15, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds the sharegpt dataset to the condition that sets ignore_eos=True for certain benchmarks. This change aligns its behavior with that of random datasets, ensuring that generation runs to the full requested length for consistent throughput measurement. While the code change is correct, the comment explaining this block is now outdated as it only refers to 'random datasets'. I've added a comment to suggest an update to the comment to improve code clarity and prevent future confusion.

# so generation runs to the requested length
if (
args.dataset_name in ("random", "random-mm")
args.dataset_name in ("random", "random-mm", "sharegpt")
Copy link
Contributor

Choose a reason for hiding this comment

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

high

By adding sharegpt here, the comment on lines 1362-1363 has become inaccurate as it only mentions 'random datasets'. To prevent future confusion, please update the comment to clarify that this logic also applies to the sharegpt dataset. For example:

# For random and sharegpt datasets, default to ignoring EOS
# so generation runs to the requested length

@Amitjoiya
Copy link
Author

Thanks for the review and the pointer — appreciated!

I've updated the comment in vllm/benchmarks/serve.py to explicitly mention both random and sharegpt datasets so the intent is clear and future confusion is avoided.

Change included as a small docs commit:

Please let me know if you'd like the comment text tweaked further. If everything looks good, reviewers can trigger the full CI (or add the ready label) for a comprehensive run. Thanks!

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

Labels

performance Performance-related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant