Qwen3.5-122B-A10B
serving recipe.

Floors are the minimum the vLLM recipe publishes across the whole replica, from vLLM's own runs. The control plane compares them with its own sizing from the model config.

• Tensor ParallelFits inside one node's interconnect. single_node_tp
• Tensor + Expert ParallelFits inside one node's interconnect. single_node_tep
• Data + Expert ParallelFits inside one node's interconnect. single_node_dep
• Multi-Node Tensor ParallelSpans nodes. multi_node_tp
• Multi-Node Data + Expert ParallelSpans nodes. multi_node_dep
• Multi-Node Tensor + Expert ParallelSpans nodes. multi_node_tep
• Prefill/Decode DisaggregationSpans nodes. pd_cluster

The recipe does not mark any hardware as verified.

Wingsmith runs models through NVIDIA Dynamo, so it serves on NVIDIA GPUs. Other vendors are listed as the recipe states them.

vllm serve Qwen/Qwen3.5-122B-A10B \
  --trust-remote-code \
  --enable-auto-tool-choice \
  --tool-call-parser qwen3_coder \
  --reasoning-parser qwen3 \
  --mm-encoder-tp-mode data

Features

• Tool callingOn by defaultEnable automatic tool choice with Qwen3 Coder parser
• ReasoningOn by defaultEnable chain-of-thought reasoning with Qwen3 parser
• Speculative decodingOpt-inMulti-token prediction speculative decoding for lower latency
• Text-only modeOpt-inSkip loading the vision encoder for text-only workloads — frees VRAM for KV cache. Mutually exclusive with encoder_parallel.
• Encoder data parallelOn by defaultRun the vision encoder in data-parallel mode — avoids TP comm overhead on the small encoder. Mutually exclusive with text_only.

1. Register the weights

   In the console, or through the API. Resolving a slug proposes an artifact and writes nothing.

   curl "http://localhost:8000/v1/artifacts/resolve?source=hf:Qwen/Qwen3.5-122B-A10B"

2. Read the draft

   The draft carries this recipe as upstream evidence: the tested flags, the precision and memory floor, the parallelism layouts, and the hardware vLLM verified, with links back to the recipe. Nothing from it is applied without you, and the draft warns when the plane's own sizing and the published floor differ by a quarter or more.

3. Create the workload

   Choose the engine, device shape and scale. The plane picks the clusters, and each cluster's operator renders the deployment as a Dynamo graph. The one recipe default it applies, --max-num-seqs, is shown above.

4. Give it an endpoint

   One model name for clients, routed by the gateway to deployments on every cluster serving it.

Run the control plane locally →

• How much GPU memory does Qwen3.5-122B-A10B need?The vLLM recipe publishes a minimum of 74 GB across the whole replica for its INT4 variant; BF16 293 GB, FP8 147 GB. That is vLLM's own measurement, not a per-GPU figure.
• Which parallelism layouts does the Qwen3.5-122B-A10B recipe support?Tensor Parallel, Tensor + Expert Parallel, Data + Expert Parallel, Multi-Node Tensor Parallel, Multi-Node Data + Expert Parallel, Multi-Node Tensor + Expert Parallel and Prefill/Decode Disaggregation.
• Can Wingsmith serve Qwen3.5-122B-A10B?Wingsmith serves models through NVIDIA Dynamo on clusters with NVIDIA GPUs. Register Qwen/Qwen3.5-122B-A10B and the plane attaches this vLLM recipe to the draft as evidence: its tested flags, precision and memory floor, for you to review rather than applied on your behalf. The recipe reports no end-to-end run on NVIDIA hardware.
• Does NVIDIA publish a Dynamo recipe for Qwen3.5-122B-A10B?Yes: 6 deployment entries for vLLM, aggregated and disaggregated. When a workload is placed, the plane defaults --max-num-seqs to the value the aggregated recipe publishes for that card, and names it on the draft.

From the vLLM recipe for Qwen/Qwen3.5-122B-A10B ↗ (snapshot at 4bcc189) and NVIDIA Dynamo's recipes at 165d854, Apache 2.0.