Skip to content

Enable CPU nightly performance benchmark and its Markdown report #18444

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 11 commits into
base: main
Choose a base branch
from

Conversation

louie-tsai
Copy link

@louie-tsai louie-tsai commented May 21, 2025

Need to standardize vLLM CPU benchmarks among customers and intel users by using vLLM benchmark suite.
Also hope to enable CPU perf numbers on vLLM performance dashboard.

Enable vLLM benchmark suite for CPU and below are snapshot of serving benchmark report.
numbers are aligned with our Xeon EMR numbers.

How to run it on CPU under vllm folder:
ON_CPU=1 bash .buildkite/nightly-benchmarks/scripts/run-performance-benchmarks.sh

also added a new section "Platform Information" section to list out CPU info

image

Here is the full report.
benchmark_results_0527_3.md

overall, it took ~2 hours for current tests.

it also needs to have auto OMP thread binding from below PR.
#17930

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.

🚀

@mergify mergify bot added the ci/build label May 21, 2025
@louie-tsai louie-tsai force-pushed the nightly_cpu_benchmark branch 7 times, most recently from 61d8f46 to b219eae Compare May 27, 2025 23:57
@louie-tsai louie-tsai force-pushed the nightly_cpu_benchmark branch from b219eae to 72d890c Compare June 2, 2025 21:51
@louie-tsai louie-tsai force-pushed the nightly_cpu_benchmark branch from 913611c to 298aba1 Compare June 3, 2025 00:21
@louie-tsai louie-tsai force-pushed the nightly_cpu_benchmark branch from e7f9de8 to 8e9e5c2 Compare June 4, 2025 00:23
@louie-tsai louie-tsai force-pushed the nightly_cpu_benchmark branch 2 times, most recently from 1299794 to 51ede3a Compare June 4, 2025 01:09
@louie-tsai
Copy link
Author

@bigPYJ1151 could you help to review this PR?

Signed-off-by: Tsai, Louie <[email protected]>
@louie-tsai louie-tsai force-pushed the nightly_cpu_benchmark branch from 2bcd0fe to 2f11d5e Compare June 4, 2025 01:34
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