Repository navigation
feat(dynamo-preproc): route with advisory EPP signals - #963
Draft
ayushag-nv wants to merge 1 commit into
Draft
ayushag-nv wants to merge 1 commit into
ayushag-nv wants to merge 1 commit into
Conversation
Signed-off-by: ayushag <ayushag@nvidia.com>
|
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
Switchyard PreProc can choose a model, but it currently has no request-specific view of that model's cache reuse or worker load. This adds an optional way to collect those signals from Dynamo EPP and use them in an SDK routing decision.
What
examples/dynamo-preproc.PROBE_CONFIGmaps eligible models to private EPP probe endpoints; observe mode records signals and routing mode passes them to the SDK.cache_awarealgorithm. Missing, stale or incomplete signals fall back to the first configured target.How
PreProc sends each eligible model's original request to its EPP, then makes one SDK decision. The gateway forwards the chosen model to its normal EPP selection path.
The policy compares
(effective_prefill_tokens + active_prefill_tokens) * relative_prefill_cost. Operators must choose models suitable for the task and configure their relative costs. This estimates prefill work; it does not assess model quality or predict end-to-end latency.Probe calls share a deadline and concurrency limit. Errors remain unknown signals. Model-specific tokenization, cumulative cache-tier estimates and actual response-usage metrics belong to the companion Dynamo draft PR #16053.
Where to Start Review
Start with
examples/dynamo-preproc/README.mdand the two new config examples. Then reviewexamples/dynamo-preproc/src/probe.rs,crates/libsy/src/algorithms/cache_aware.rsand its Runner configuration.Metadata::serving_observationsis supplied by the host, never parsed from caller headers.Test Plan
The live check used Dynamo 1.5.0 SGLang workers and the existing agentgateway v1.5.0 Dynamo build. This is functional validation, not a production latency benchmark. The probe client requires the companion Dynamo change; CPU/disk cache residency was not exercised.
Part of SWITCH-1627.