bench: add prod2048 config (runner batch sizes on chat profile); docs: ubatch 4096 results

docs/kairic-edge.md

@@ -211,7 +211,8 @@ See [[deployment]] for the update process.
 |---------|-------|--------|
 | Bind | `0.0.0.0:52625` | Local (runner default `127.0.0.1:8080`) |
 | Context | 262144, 1 slot | Pinned runner |
-| Batch / ubatch | 4096 / 2048 | Local (runner: 2048 / 512) |
+| Batch / ubatch | 4096 / 4096 | Local (runner: 2048 / 512; v3: 4096 / 4096) |
+| Model loading | `--no-mmap` | Local (benchmarks: no perf difference) |
 | Threads | 16 target / 32 batch | Pinned runner |
 | KV | f16 target and draft | Pinned runner |
 | Prompt cache | `--cache-ram 8192 --cache-prompt --cache-idle-slots -ctxcp 32` | Pinned runner |
@@ -227,8 +228,12 @@ Local deviations and their reasons:
 - **Reasoning on + deepseek**: thinking goes to `message.reasoning_content`,
   matching the retired v3 service. `preserve_thinking=true` keeps thinking
   tokens in the history across turns.
-- **Batch 4096 / ubatch 2048**: larger than the runner; unified memory has
-  headroom. Prefill and decode match the runner profile in benchmarks.
+- **Batch 4096 / ubatch 4096**: larger than the runner; matches the
+  retired v3 profile. Unified memory has headroom. Ubatch 4096 slows
+  prefill (~25% versus ubatch 2048, ~50% versus the runner's ubatch 512)
+  and does not change decode.
+- **`--no-mmap`**: benchmarks show no performance difference versus mmap.
+  Kept per operator preference (2026-08-22).
 - **Target greedy argmax fast path off**: the pinned runner sets
   `LLAMA_TARGET_GREEDY_ARGMAX_FASTPATH=1`. That fast path fails closed on
   any non-greedy request (400 error). The model card's own chat
@@ -255,7 +260,8 @@ Findings:
 
 - Prefill runs 1.5-2.3x faster than v3 at every depth.
 - Prose decode runs 15-26% slower than v3 at every depth.
-- `--no-mmap` makes no difference (19.89 vs 19.80 t/s decode).
+- `--no-mmap` makes no difference (19.89 vs 19.80 t/s decode). The
+  service now runs `--no-mmap` per operator preference.
 - `-c 262144` versus `-c 8192` makes no difference to decode.
 - Live service at ~116k context: 13.5-14.9 t/s, consistent with the 64k
   bench. Long conversations run in the deep-context regime.
@@ -266,6 +272,23 @@ Findings:
   represent prose chat. The card's natural-prose slice measured 34.88
   t/s on the certified system.
 
+### ubatch 4096 + --no-mmap profile (2026-08-22)
+
+The production profile moved from batch 4096 / ubatch 2048 with mmap to
+batch 4096 / ubatch 4096 with `--no-mmap` (matching the v3 profile). Same
+harness, same prompts.
+
+| Context | ub2048 decode (cold/warm) | ub4096 decode (cold/warm) | ub2048 prefill cold | ub4096 prefill cold |
+|---------|---------------------------|---------------------------|---------------------|---------------------|
+| ~8k | 19.79 / 19.36 | 22.65 / 19.78 | 348 | 266 |
+| ~16k | 19.83 / 18.75 | 18.13 / 22.48 | 370 | 258 |
+| ~64k | 14.61 / - | 14.11 / 13.80 | 232 | 203 |
+
+Ubatch 4096 does not change decode at any depth. It slows prefill by
+~25% versus ubatch 2048 and ~50% versus the runner's ubatch 512
+(506 t/s at 8k). The IU4 lane accelerates 96-512-row prompt and
+verification shapes; large ubatches do not use those shapes.
+
 ## Rollback to v3
 
 The v3 payload and binary stay on the machine for rollback.