Skip to content

[Misc] Fix duplicate FusedMoEConfig debug messages #21455

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

Merged
merged 1 commit into from
Jul 24, 2025

Conversation

njhill
Copy link
Member

@njhill njhill commented Jul 23, 2025

A huge number of these are logged currently (per worker, per layer)

(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
(DPEngineCoreActor pid=81393) DEBUG 07-23 07:44:18 [config.py:328] Using FusedMoEConfig::max_num_tokens=256
...

A huge number of these are logged currently (per worker, per layer)

Signed-off-by: Nick Hill <nhill@redhat.com>
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.

Code Review

This pull request addresses an issue with excessive duplicate debug messages from FusedMoEConfig. The change correctly replaces logger.debug with logger.debug_once, which leverages an LRU cache to ensure the message is logged only once per unique configuration within a worker. This is an effective and clean fix that improves log clarity without introducing any issues. The change is approved.

@robertgshaw2-redhat robertgshaw2-redhat enabled auto-merge (squash) July 23, 2025 12:53
@github-actions github-actions bot added the ready ONLY add when PR is ready to merge/full CI is needed label Jul 23, 2025
@vllm-bot vllm-bot merged commit f0f4de8 into vllm-project:main Jul 24, 2025
79 of 81 checks passed
@njhill njhill deleted the rm-moe-debug-spam branch July 24, 2025 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready ONLY add when PR is ready to merge/full CI is needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants