Repository navigation
[Fix] Enable chunked input-logprob processing by default to cap peak memory - #31498
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
/rerun-test registered/pp/test_pp_single_node.py |
|
Results for 🚀 🚀 🚀 |
|
Results for 🚀 |
|
/tag-and-rerun-ci |
|
Results for 🚀 |
|
Results for 🚀 🚀 |
|
/rerun-test registered/pp/test_pp_single_node.py |
|
/tag-and-rerun-ci |
Large
return_logprobprefill batches materialize two near-identical fp32[rows, vocab]logits tensors (~4.4 GiB each at ~7.8k rows on a 152k vocab), which can OOM an almost-full GPU. Behavior change: flipSGLANG_ENABLE_LOGITS_PROCESSER_CHUNKdefault toTrueso batches above 2048 input-logprob rows take the existing chunked path (peak memory becomes chunk-sized and batch-independent); batches at or below the threshold are unaffected, and the env var remains as an opt-out. Also keep per-chunk_get_logitscalls off the shared graph logits buffer to rule out chunk aliasing, and add forced multi-chunk stitching tests.CI States
Latest PR Test (Base): 🚫 Run #29608756604
Latest PR Test (Extra): ❌ Run #29608756846