docs: document sglang maintenance workflow
This commit is contained in:
12
README.md
12
README.md
@@ -35,8 +35,10 @@ Sync the environment:
|
||||
uv sync
|
||||
```
|
||||
|
||||
Local experiments can use a repo-local `third_party/sglang` checkout of SGLang
|
||||
`v0.5.10`, but that heavyweight checkout is intentionally not committed here.
|
||||
`third_party/sglang` vendors a clean SGLang `v0.5.10` snapshot plus our local
|
||||
PD/session-cache patches in later commits. Keep SGLang changes scoped under that
|
||||
directory and commit them with `feat(sglang): ...` or `fix(sglang): ...` so they
|
||||
stay easy to review against the vendor baseline.
|
||||
|
||||
## CLI
|
||||
|
||||
@@ -126,9 +128,9 @@ Notes:
|
||||
- Live benchmarking uses the repo-local `agentic_pd_hybrid.pd_router`, which
|
||||
preserves the real prefill/decode double-request path over loopback without
|
||||
depending on the upstream Rust router build.
|
||||
- Managed live benchmarking prefers a local
|
||||
`third_party/sglang/python/sglang` checkout when it exists, so local SGLang
|
||||
source changes can apply immediately without packaging a wheel.
|
||||
- Managed live benchmarking prefers the vendored
|
||||
`third_party/sglang/python/sglang` source tree, so local SGLang changes apply
|
||||
immediately without packaging a wheel.
|
||||
- Live benchmarking currently targets the `mooncake` transfer backend, because
|
||||
`mooncake-transfer-engine` is installed and usable on this node.
|
||||
- `benchmark-live` and `replay` support streaming by default for TTFT/TPOT
|
||||
|
||||
Reference in New Issue
Block a user