[Feature] Add --attn-dp-size and deprecate --enable-dp-attention

.agents/skills/cookbook-add-model/references/authoring-reference.md

@@ -134,7 +134,7 @@ Each cell describes one verified (or auto-estimated) launch recipe.
 - DO NOT include `--host` / `--port` literally — use `{{HOST_IP}}` /
   `{{PORT}}` placeholders so users can override through the Env modal.
 - Order flags as: `--model-path` first (after any `--trust-remote-code`),
-  then parallelism (`--tp`, `--dp`, `--enable-dp-attention`), then MoE
+  then parallelism (`--tp`, `--attn-dp-size`), then MoE
   flags, then tuning knobs, with `--host` / `--port` last. The playground
   engine assumes this ordering when inserting overrides (its anchors target
   `--model-path` / `--tp` / etc., and inserts before the `--host` tail).
@@ -171,7 +171,7 @@ schemas (full reference in the `_playground.jsx` header):
 
 | Axis key | Widget | Use when |
 |---|---|---|
-| `attention` | TP / CP / DP-Attention sub-knobs (DP-Attention is a combined knob: its value is the DP degree AND toggles `--enable-dp-attention`) | Model exposes parallelism knobs in its cells (§2.2) and you want users to override them. |
+| `attention` | TP / CP / DP-Attention sub-knobs (DP-Attention is a single knob: its value is the attention DP size, emitted as `--attn-dp-size N`) | Model exposes parallelism knobs in its cells (§2.2) and you want users to override them. |
 | `moe` | Backend select (incl. MegaMoE) + EP knob; picking the MegaMoE backend reveals a Quantization sub-select (W4A8/W4A4) | Model is MoE and supports multiple `--moe-*-backend` choices. For Blackwell MoE kernel-fusion, give the `megamoe` backend option a `requiresHw` (and optional `excludesStrategy`) gate, then add a sibling `megamoeQuant` block (`{stripEnv, options}`): W4A8 = `NUM_MAX` only, W4A4 adds the FP4-activations env vars; both strip the DeepEP dispatch env. |
 | `parsers` | Multi-toggle | Model has reasoning / tool-call parsers. |
 | `speculative` | Single-select chip group | Model has spec-decoding presets you want to expose. |
@@ -208,7 +208,7 @@ schemas (full reference in the `_playground.jsx` header):
   knobs/values that are disabled under the live facts, so stale picks never
   emit a blocked combination. Interleave prefill-CP + DP-Attention is
   deliberately NOT grayed (combined support is planned upstream even though
-  current releases assert `dp_size == 1` for interleave) — the engine shows
+  current releases assert `attn_dp_size == 1` for interleave) — the engine shows
   a warning hint below the command box instead.
 - The CP knob emits `--attn-cp-size N --enable-prefill-cp --cp-strategy S`,
   where S is: an optional `{ id: "cpStrategy", values: [null, "interleave",

.agents/skills/cookbook-add-model/templates/config.jsx.tmpl

@@ -176,7 +176,7 @@ sgl-eval run gsm8k \\
   playgroundFeatures: {
 
     // ----- Card: "Attention Parallelism" -----  KEEP if the model exposes TP/CP/DP
-    // knobs. DP-Attention is a combined knob: value = DP degree AND toggles `--enable-dp-attention`.
+    // knobs. DP-Attention is a single knob: value = attention DP size, emitted as `--attn-dp-size N`.
     attention: {
       knobs: [
         { id: "tp", label: "TP", values: [
@@ -357,8 +357,7 @@ sgl-eval run gsm8k \\
         "--trust-remote-code",
         "--model-path {{MODEL_NAME}}",
         "--tp 4",
-        "--dp 4",
-        "--enable-dp-attention",
+        "--attn-dp-size 4",
         "--moe-a2a-backend deepep",
         "--host {{HOST_IP}}",
         "--port {{PORT}}",
@@ -403,8 +402,7 @@ sgl-eval run gsm8k \\
         "--trust-remote-code",
         "--model-path {{MODEL_NAME}}",
         "--tp 16",
-        "--dp 16",
-        "--enable-dp-attention",
+        "--attn-dp-size 16",
         "--moe-a2a-backend deepep",
         "--host {{HOST_IP}}",
         "--port {{PORT}}",

.agents/skills/cookbook-migrate-model/SKILL.md

@@ -118,7 +118,7 @@ that **changes other parts of the command** (TP, mem) must (the Playground
 can't do coupled changes), and so does a toggle the legacy page itself labels
 with operating-point words — e.g. a `dpattention` radio whose options are
 subtitled "Low Latency" / "High Throughput" (GLM-5.1 / Kimi-K2.6 pattern) —
-even when its flags are uncoupled (`--dp N --enable-dp-attention` is a pure
+even when its flags are uncoupled (`--attn-dp-size N` is a pure
 flag add). Any other toggle that only adds/removes its own flags becomes a
 Playground axis with the flags baked into cells when the legacy default was
 ON — EXCEPT parsers:

.agents/skills/cookbook-migrate-model/references/dimension-mapping.md

@@ -12,7 +12,7 @@ this file is about the *mapping decisions*.
 | hardware radio | `match.hw` | Catalog ids as-is. Off-catalog hardware → `config.hardware` entry — e.g. A100 `{id:"a100", label:"A100", vram:"80GB", vendor:"nvidia"}` (merges into the NVIDIA row), Xeon `{id:"xeon", label:"Xeon", vram:"host RAM", vendor:"intel"}` (engine renders a new INTEL row; any vendor key works). A merged chip like GLM-5's "MI300X/MI325X" splits into two ids with duplicated cells (cells are denormalized by design). |
 | model-size / model-name radio | `variants` | One variant per deployable checkpoint family; single `{id:"default"}` when there's no variant axis (then `modelNames` keys drop the variant half). |
 | quantization radio | `quantizations` | Real precision ids (`bf16`/`fp8`/`fp4`/`int4`/…). One `fp4` id even when checkpoints differ per vendor — route via `hw\|variant\|quant` triple keys in `modelNames` (NVFP4 on Blackwell vs AMD MXFP4 is the precedent); per-hw greying falls out of which cells exist. |
-| toggle that **couples** with other parts of the command (changes TP/mem/EP), OR one the legacy page labels with **operating-point words** | `strategies` | The Playground applies pure flag diffs — it cannot do coupled changes. Example: Qwen3.5's MTP toggle bumps TP on three H100 combos → strategies `low-latency` (MTP on) / `high-throughput` (MTP off). **Naming counts like coupling**: GLM-5.1's / Kimi-K2.6's `dpattention` adds only `--dp N --enable-dp-attention` (uncoupled), but its options are subtitled "Low Latency" / "High Throughput" — the page's own named operating-point split → strategies; a flag-only spec toggle riding alongside it stays a Playground axis and bakes per its legacy default. GPU-count radios (GLM-4.7, MiniMax-M2.5/2.7) → budget-tier strategies with the legacy SUPPORT matrix preserved by which cells exist. Strategy count follows the page's operating points: 1 → `balanced`, 2 → `low-latency`+`high-throughput`, 3 → the full trio (§4). |
+| toggle that **couples** with other parts of the command (changes TP/mem/EP), OR one the legacy page labels with **operating-point words** | `strategies` | The Playground applies pure flag diffs — it cannot do coupled changes. Example: Qwen3.5's MTP toggle bumps TP on three H100 combos → strategies `low-latency` (MTP on) / `high-throughput` (MTP off). **Naming counts like coupling**: GLM-5.1's / Kimi-K2.6's `dpattention` adds only `--attn-dp-size N` (uncoupled), but its options are subtitled "Low Latency" / "High Throughput" — the page's own named operating-point split → strategies; a flag-only spec toggle riding alongside it stays a Playground axis and bakes per its legacy default. GPU-count radios (GLM-4.7, MiniMax-M2.5/2.7) → budget-tier strategies with the legacy SUPPORT matrix preserved by which cells exist. Strategy count follows the page's operating points: 1 → `balanced`, 2 → `low-latency`+`high-throughput`, 3 → the full trio (§4). |
 | toggle that only adds/removes its own flags | Playground axis (+ bake, EXCEPT parsers and accuracy-degrading flags) | **Parsers (`--reasoning-parser` / `--tool-call-parser`) are NEVER baked into cells** — Deployment commands ship without them regardless of the legacy default or the measured command; the `parsers` axis adds them on top (DSv4 convention; cells mirror the legacy generator's parsers-OFF output). Accuracy-degrading toggles are never baked either — §2 caveats (axis-only, accuracy-safe cells). Other flag-only toggles: legacy default ON → bake into cells AND declare the axis so users can strip (red strikethrough); default OFF → keep cells clean, axis preset only. MTP/EAGLE presets → `speculative` axis; dp-attention → a strategy when the legacy page labels it as the operating-point split or when coupled (see the row above), else `attention.dpAttn`. **EVERY legacy control survives as an interactive control** (a dimension or a Playground axis), never a tips-only mention — but a model-specific control is **config DATA, not engine code**: the axis handler reads options/flags/env/gating straight from `config.playgroundFeatures` (MegaMoE W4A4 is entirely DSv4 config data on the existing `moe` axis — no per-model engine edit). A control that fits an existing axis's data schema is therefore pure config, full stop. A **titled single-select that strips a flag family** (e.g. Nemotron3's "KV Cache DType" `--kv-cache-dtype`) is covered by the merged generic **`flagSelects`** axis → **config-only**: declare a `flagSelects` list of `{ id, title, stripPrefixes, options }` (see the Qwen3.5 mamba example), **no engine PR**. Only a control whose *shape* `flagSelects` still can't express would need a new ONE-TIME generic primitive (never a model-named handler) on a prior engine PR; the backward-compat reasoning (opt-in per key, not in the opt-out set) is in engine-axis.md. |
 | per-combo hidden option (e.g. spec hidden on Xeon) | absent cells | Don't create cells for combos the legacy widget couldn't produce; the engine greys them automatically. `# Error:` pseudo-commands → no cell + explanation in §2 tips and/or a chip `disable`/`disableReason`. |
 | coupled secondary knob (e.g. mamba cache V1/V2) | cells + Playground axis | Bake the correct value per cell following the legacy coupling (Qwen3.5: MTP ⇒ `--mamba-radix-cache-strategy extra_buffer` on NVIDIA; AMD/Xeon ⇒ V1/no flag) and document the coupling in §2 tips — AND surface the knob as a Playground axis like every other legacy feature (row above; add the axis when none fits). Baking alone is NOT enough — the every-feature rule supersedes the pilot's cells+prose-only treatment of Qwen3.5's mamba knob (retrofit pending). The mamba knob is the same single-select shape as KV Cache DType, so it rides the merged generic **`flagSelects`** axis — Qwen3.6 / Qwen3-Coder-Next declare it purely in config (a `flagSelects` block), **no engine PR**. |
@@ -30,7 +30,7 @@ this file is about the *mapping decisions*.
 | (absent) | append `--host {{HOST_IP}}`, `--port {{PORT}}` to every cell |
 | `--nnodes N --node-rank … --dist-init-addr …` literals | delete; `match.nodes: "multi-N"` + `nodesOptions` entry — the engine injects the trio after the last parallelism anchor plus the multi-node header comment |
 | env-var command prefixes | verbatim into `cell.env[]` (never drop/normalize) |
-| flag order as emitted | re-sort to canonical: `--trust-remote-code` → `--model-path` → parallelism (`--tp`/`--dp`/`--enable-dp-attention`/EP) → MoE → tuning → `--host`/`--port` (Playground insert anchors assume this). Keep the legacy relative order within the tuning span so commands stay eyeball-diffable. |
+| flag order as emitted | re-sort to canonical: `--trust-remote-code` → `--model-path` → parallelism (`--tp`/`--attn-dp-size`/EP) → MoE → tuning → `--host`/`--port` (Playground insert anchors assume this). Keep the legacy relative order within the tuning span so commands stay eyeball-diffable. |
 
 Caveats discovered in the pilot:
 - The Playground `moe.ep` knob only understands `--ep` — normalize a legacy

.agents/skills/sglang-runtime-context/SKILL.md

@@ -227,7 +227,7 @@ slack (`>= len(...) - 1`) or compared key names instead of value sources.
 read-through over the canonical getters, so they answer with the live process
 groups. Everything else — `tp_size`, `pp_size`, `attn_cp_size`, `dcp_size`,
 `moe_dp_size` included, alongside config-only leaves like `nccl_port`,
-`enable_dp_attention`, `dp_size`, `ep_size`, `dwdp_size` — is answered from the
+`dp_size`, `ep_size`, `dwdp_size` — is answered from the
 published `parallel` bag. Reading a leaf before publish raises a `ValueError`
 naming the namespace; an unknown name is an `AttributeError`.
 

benchmark/deepseek_v3/README.md

@@ -47,7 +47,7 @@ Add [performance optimization options](#performance-optimization-options) as nee
 
 [MLA optimizations](https://lmsys.org/blog/2024-09-04-sglang-v0-3/#deepseek-multi-head-latent-attention-mla-throughput-optimizations) are enabled by default. Here are some optional optimizations can be enabled as needed.
 
-- [Data Parallelism Attention](https://lmsys.org/blog/2024-12-04-sglang-v0-4/#data-parallelism-attention-for-deepseek-models): For high QPS scenarios, add the `--enable-dp-attention` argument to boost throughput.
+- [Data Parallelism Attention](https://lmsys.org/blog/2024-12-04-sglang-v0-4/#data-parallelism-attention-for-deepseek-models): For high QPS scenarios, add the `--attn-dp-size <N>` argument (e.g. equal to `--tp`) to boost throughput.
 - [Torch.compile Optimization](https://lmsys.org/blog/2024-09-04-sglang-v0-3/#torchcompile-latency-optimizations): Add `--enable-torch-compile` argument to enable it. This will take some time while server starts. The maximum batch size for torch.compile optimization can be controlled with `--torch-compile-max-bs`. It's recommended to set it between `1` and `8`. (e.g., `--torch-compile-max-bs 8`)
 
 ### Usage: Chat with DeepSeek

docs/cookbook/autoregressive/DeepSeek/DeepSeek-Math-V2.mdx

@@ -52,7 +52,7 @@ This section provides deployment configurations optimized for different hardware
 **DP Attention:**
 
 - Enable DP attention for high-throughput scenarios
-- The `--dp` value commonly matches the `--tp` value
+- The `--attn-dp-size` value commonly matches the `--tp` value
 - Trade-off: Higher throughput at the cost of slightly increased latency
 
 ## 4. Model Invocation

docs/cookbook/autoregressive/DeepSeek/DeepSeek-OCR-2.mdx

@@ -192,8 +192,6 @@ sglang serve \
   --enable-multimodal \
   --tp 1 \
   --ep 1 \
-  --dp 1 \
-  --enable-dp-attention \
   --host 0.0.0.0 \
   --port 30000
 ```

docs/cookbook/autoregressive/DeepSeek/DeepSeek-OCR.mdx

@@ -184,8 +184,6 @@ python3 -m sglang.launch_server \
   --model-path deepseek-ai/DeepSeek-OCR \
   --tp 1 \
   --ep 1 \
-  --dp 1 \
-  --enable-dp-attention \
   --dtype float16 \
   --host 0.0.0.0 \
   --port 8000

docs/cookbook/autoregressive/DeepSeek/DeepSeek-R1.mdx

@@ -95,7 +95,7 @@ DeepSeek-R1 shares the same MoE architecture as DeepSeek-V3, so the same hardwar
 python3 -m sglang.compile_deep_gemm --model deepseek-ai/DeepSeek-R1 --tp 8 --trust-remote-code
 ```
 
-**Data Parallelism Attention (`--enable-dp-attention`):** Recommended for high-throughput scenarios. Use `--enable-dp-attention --tp 8 --dp 8` on a single 8-GPU node.
+**Data Parallelism Attention (`--attn-dp-size`):** Recommended for high-throughput scenarios. Use `--tp 8 --attn-dp-size 8` on a single 8-GPU node.
 
 **NCCL timeout:** If model loading is slow, increase: `--dist-timeout 3600`.
 

docs/cookbook/autoregressive/DeepSeek/DeepSeek-V3.mdx

@@ -75,7 +75,7 @@ python3 -m sglang.compile_deep_gemm --model deepseek-ai/DeepSeek-V3 --tp 8 --tru
 ```
 DeepGEMM is enabled by default on Hopper/Blackwell and can be disabled with `SGLANG_ENABLE_JIT_DEEPGEMM=0`.
 
-**Data Parallelism Attention (`--enable-dp-attention`):** Recommended for high-throughput scenarios with large batch sizes. Reduces KV-cache duplication across TP ranks. Use `--enable-dp-attention --tp 8 --dp 8` on a single 8-GPU node. Not recommended for low-latency, small-batch workloads.
+**Data Parallelism Attention (`--attn-dp-size`):** Recommended for high-throughput scenarios with large batch sizes. Reduces KV-cache duplication across TP ranks. Use `--tp 8 --attn-dp-size 8` on a single 8-GPU node. Not recommended for low-latency, small-batch workloads.
 
 **NCCL timeout:** If model loading is slow and you hit an NCCL timeout, increase it: `--dist-timeout 3600`.
 
@@ -454,8 +454,7 @@ We use SGLang's built-in benchmarking tool to conduct performance evaluation on
 python3 -m sglang.launch_server \
   --model-path deepseek-ai/DeepSeek-V3 \
   --tp 8 \
-  --dp 8 \
-  --enable-dp-attention \
+  --attn-dp-size 8 \
   --speculative-algorithm EAGLE \
   --speculative-num-steps 3 \
   --speculative-eagle-topk 1 \
@@ -529,8 +528,7 @@ python3 -m sglang.launch_server \
   --model-path deepseek-ai/DeepSeek-V3 \
   --tp 8 \
   --ep 8 \
-  --dp 8 \
-  --enable-dp-attention \
+  --attn-dp-size 8 \
   --host 0.0.0.0 \
   --port 8000
 ```

docs/cookbook/autoregressive/DeepSeek/DeepSeek-V3_1.mdx

@@ -73,7 +73,7 @@ python3 -m sglang.compile_deep_gemm --model deepseek-ai/DeepSeek-V3.1 --tp 8 --t
 ```
 DeepGEMM is enabled by default on Hopper/Blackwell and can be disabled with `SGLANG_ENABLE_JIT_DEEPGEMM=0`.
 
-**Data Parallelism Attention (`--enable-dp-attention`):** Recommended for high-throughput scenarios with large batch sizes. Reduces KV-cache duplication across TP ranks. Use `--enable-dp-attention --tp 8 --dp 8` on a single 8-GPU node. Not recommended for low-latency, small-batch workloads.
+**Data Parallelism Attention (`--attn-dp-size`):** Recommended for high-throughput scenarios with large batch sizes. Reduces KV-cache duplication across TP ranks. Use `--tp 8 --attn-dp-size 8` on a single 8-GPU node. Not recommended for low-latency, small-batch workloads.
 
 **NCCL timeout:** If model loading is slow and you hit an NCCL timeout, increase it: `--dist-timeout 3600`.