Skip to content

[BugFix] fix dp sheduler bug in ep4tp1 when start by using multi_api_server#6598

Open
ddchenhao66 wants to merge 2 commits intoPaddlePaddle:developfrom
ddchenhao66:adapter_ep4tp1
Open

[BugFix] fix dp sheduler bug in ep4tp1 when start by using multi_api_server#6598
ddchenhao66 wants to merge 2 commits intoPaddlePaddle:developfrom
ddchenhao66:adapter_ep4tp1

Conversation

@ddchenhao66
Copy link
Collaborator

Motivation

使用multi_api_server时,不同dp的EngineService是独立的,各自拥有自己的dp scheduler,所以不再需要持有其他进程的通信队列

Modifications

为简化修改量,暂时仍使用multiprocessing.Queue;

  1. api_server.py启动时设置各自的队列
  2. dp_scheduler的队列列表只包含一个队列

Usage or Command

Accuracy Tests

Checklist

  • Add at least a tag in the PR title.
    • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
    • You can add new tags based on the PR content, but the semantics must be clear.
  • Format your code, run pre-commit before commit.
  • Add unit tests. Please write the reason in this PR if no unit tests.
  • Provide accuracy results.
  • If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

@paddle-bot
Copy link

paddle-bot bot commented Mar 2, 2026

Thanks for your contribution!

@codecov-commenter
Copy link

codecov-commenter commented Mar 2, 2026

Codecov Report

❌ Patch coverage is 63.63636% with 4 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (develop@ecfd088). Learn more about missing BASE report.

Files with missing lines Patch % Lines
fastdeploy/scheduler/dp_scheduler.py 62.50% 3 Missing ⚠️
fastdeploy/engine/expert_service.py 50.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             develop    #6598   +/-   ##
==========================================
  Coverage           ?   71.78%           
==========================================
  Files              ?      394           
  Lines              ?    53933           
  Branches           ?     8463           
==========================================
  Hits               ?    38718           
  Misses             ?    12433           
  Partials           ?     2782           
Flag Coverage Δ
GPU 71.78% <63.63%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

rainyfly
rainyfly previously approved these changes Mar 4, 2026
Copy link
Collaborator

@rainyfly rainyfly left a comment

Choose a reason for hiding this comment

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

LGTM

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants