add prefix warmup to prime cache before server startup - #9
Merged
Conversation
new --prefix-warmup-file flag runs chat warmup requests before serve_http; aborts startup on failure
Tushar-ml
marked this pull request as ready for review
June 3, 2026 12:18
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.
Adds
--prefix-warmup-file: runs chat warmup requests through the engine before/healthis exposed, to prime the prefix/KV cache and absorb one-time JIT/CUDA-graphcosts (pod warmup). Warmup goes through the normal chat path (template/tokenization match
real traffic). Fatal on failure.
Test Plan
gemma-4-31B-FP8, 100 cold-start requests, 10k input (7k shared prefix) / 50 output, with
vs without
--prefix-warmup-file.Test Result
Warmup runs before
/health(verified in logs); steady-state unchanged; startup tail removed.