[llm.serving] Reconfigure router to better perform under high concurrency #50876
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 are these changes needed?
Accordingly to internal benchmarks the router deployment becomes bottleneck under high concurrency situation. This PR reconfigured the router to use a shorter target ongoing request (16) to better scales the router. And to make router's
min_replicas,initial_replicas, andmax_replicasto be a factor of N out of all the models. The multiplication factor can also be configured via env varRAYLLM_ROUTER_TO_MODEL_REPLICA_RATIOand is defaulted to 2 (meaning there will be roughly 2 router replicas for every model replica)Benchmark plot:

Fixed number of router replicas + different amount of model replicas
Variable number of router replicas + model replicas

Related issue number
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.