LatencyPredictionScorer for PD #564
Open
+529
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🚨 Unsigned commits detected! Please sign your commits. For instructions on how to set up GPG/SSH signing and verify your commits, please see GitHub Documentation. |
RishabhSaini
changed the title
- Add PDPredictionRequestBuilder to populate PodType from llm-d.ai/role labels - Add pd-slo-aware-scorer plugin wrapping slo_aware_router with P/D builder - Register pd-slo-aware-scorer in plugin registry - Add example EPP config for P/D SLO-aware scheduling (pd-slo-epp-config.yaml) - Add comprehensive guide on P/D SLO scheduling (docs/pd-slo-aware-scheduling.md) Enables separate latency prediction models for prefill vs decode workloads.
RishabhSaini
force-pushed
the
sloAwareRouter
branch
from
d260dd4 to
043579b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Blocked on GAIE