Skip to content

add some examples for other benchmark scripts #19893

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

reidliu41
Copy link
Contributor

@reidliu41 reidliu41 commented Jun 20, 2025

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.

Purpose

  • add some examples for other benchmark scripts

Test Plan

Test Result

(Optional) Documentation Update

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.

🚀

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.

Summary of Changes

Hello @reidliu41, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the benchmarks/README.md file by adding a variety of new example commands for several existing benchmark scripts. The additions aim to provide clearer guidance and ready-to-use configurations for users looking to test structured output generation, long document QA throughput, prefix caching, and request prioritization within the system.

Highlights

  • Structured Output Benchmarking Examples: Added comprehensive examples for benchmark_serving_structured_output.py, covering various structured generation types such as JSON schema, grammar-based, regex-based, choice-based, and XGrammar datasets. This includes the necessary server setup command.
  • Long Document QA Throughput Benchmarking Examples: Included new examples for benchmark_long_document_qa_throughput.py, demonstrating how to benchmark long document question-answering with prefix caching, including basic tests and different prompt repetition modes (random, tile, interleave).
  • Prefix Caching Benchmarking Examples: Provided examples for benchmark_prefix_caching.py to illustrate the efficiency of automatic prefix caching, with scenarios for fixed prompts and usage with the ShareGPT dataset.
  • Request Prioritization Benchmarking Examples: Added examples for benchmark_prioritization.py, showcasing how to benchmark request prioritization within vLLM, covering basic prioritization tests and scenarios involving multiple sequences per prompt.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

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 valuable examples for several benchmark scripts to the benchmarks/README.md file, covering structured output, long document QA, prefix caching, and request prioritization. The documentation is generally clear and well-structured, making it easier for users to understand how to run these benchmarks.

One minor correction is needed for an incorrect script path in one of the examples.

Additionally, the PR description checklist is largely unfilled. While this PR primarily adds documentation, completing relevant sections of the checklist (like confirming no further documentation updates are needed beyond this PR) can be helpful for maintainers.

### Multiple Sequences per Prompt

```bash
python3 benchmark_prioritization.py \
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The path to the benchmark_prioritization.py script seems to be missing the benchmarks/ directory prefix. Users copying this command will likely encounter a 'file not found' error.

All other benchmark scripts in this README are invoked with python3 benchmarks/<script_name>.py.

Suggested change
python3 benchmark_prioritization.py \
python3 benchmarks/benchmark_prioritization.py \

@reidliu41 reidliu41 force-pushed the add-benchmark-examples branch from c3bed8b to 2a9bae3 Compare June 20, 2025 06:36
@reidliu41
Copy link
Contributor Author

hi @houseroad @ywang96 could you please help to take a look if you have time? thanks a lot

@mergify mergify bot added the performance Performance-related issues label Jun 22, 2025
@reidliu41
Copy link
Contributor Author

hi team, can someone help to take a look? 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