Skip to content

[None][fix] Stop forcing Mixed hybrid manager for PYTHON transceiver runtime#3

Open
lingjiew wants to merge 1 commit into
nv-guomingz:user/guomingz/qwen3.5_agentxfrom
lingjiew:user/lingjiew/fix-python-runtime-hybrid-manager
Open

[None][fix] Stop forcing Mixed hybrid manager for PYTHON transceiver runtime#3
lingjiew wants to merge 1 commit into
nv-guomingz:user/guomingz/qwen3.5_agentxfrom
lingjiew:user/lingjiew/fix-python-runtime-hybrid-manager

Conversation

@lingjiew

@lingjiew lingjiew commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Bug

In _util.py hybrid manager selection, transceiver_runtime == 'PYTHON' force-selects MixedMambaHybridCacheManager. The rule predates this branch's V2 disagg support (d19e249): KvCacheTransceiverV2 now drives V2MambaHybridCacheManager natively.

Effect today:

  • with enable_block_reuse=True the rule is dead code (the reuse branch returns the V2 manager a few lines earlier);
  • with reuse disabled it silently downgrades PYTHON-runtime deployments to the Mixed manager instead of the default V2 manager, and forces launcher-side workarounds (our benchmark harness has to avoid transceiver_runtime: PYTHON entirely and reach the python transceiver via the V2-manager isinstance re-route).

Fix

Remove the override; PYTHON runtime now selects managers exactly like CPP/unset does. Mixed remains available via TLLM_MAMBA_MANAGER_PREFERENCE=MIXED.

Validation

The resulting pairing (V2MambaHybridCacheManager + KvCacheTransceiverV2) is the one validated end-to-end on Qwen3.5-397B-A17B-NVFP4 GB300 disagg: 37-point ctx-only sweep + 52-point gen-only sweep, KV reuse realized 93-94%, conversation-affinity ADP routing and MTP forced-AL all green (2026-07-06).

Related: #2 (ADP dummy-slot guard), and a sibling PR adding logging/validation to the transceiver factory.

🤖 Generated with Claude Code

…runtime

The transceiver_runtime=='PYTHON' -> MixedMambaHybridCacheManager rule
predates V2 disagg support: KvCacheTransceiverV2 now drives
V2MambaHybridCacheManager natively (d19e249). With block reuse
enabled the rule was already dead code (the reuse branch returns the V2
manager earlier); with reuse disabled it silently downgraded
PYTHON-runtime deployments to the Mixed manager instead of the default
V2 manager. Remove it — Mixed remains available via
TLLM_MAMBA_MANAGER_PREFERENCE=MIXED.

The V2 manager + KvCacheTransceiverV2 pairing is validated end-to-end
on Qwen3.5-397B-A17B GB300 disagg (37-point ctx-only + 52-point
gen-only sweeps, realized KV reuse 93-94%).

Signed-off-by: Lingjie Wu <lingjiew@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant