THE SOURCE IN CONTEXT
The pinned Qwen-Image-2.1 recipe defaults to Qwen/Qwen-Image-2.1 (bf16). Its effective default-variant minimum is vLLM 0.29.0. Select the exact variant, hardware override and topology before treating it as a launch plan. No deployment was run by this site.
Which artifact and engine does this recipe select?
The recipe identifies Qwen/Qwen-Image-2.1 as its model family entry and selects Qwen/Qwen-Image-2.1 by default. The default precision label is bf16; model-wide and variant-specific runtime requirements are kept separately below. The document revision fixes what the recipe said, while the weight revision and executed runtime revision remain separate fields. A model-family title alone cannot establish either artifact identity.
Source: vllm-project · pinned document
What needs special attention for this model?
This is image generation through vLLM-Omni, not a text decode benchmark. The YAML’s context-length zero is a not-applicable sentinel, not a zero-token model. The BF16 description reports a 34.0 GB peak on one GB300 at 1024×1024, 40 steps, CFG off and VAE tiling; its 40 GB planning minimum is a separate derived budget. Do not express image performance in language-model tokens per second.
Source: vllm-project · pinned document
How should the settings be applied?
Choose one artifact variant and one hardware profile from the original recipe, then resolve its shared, variant, hardware, strategy and optional-feature settings together. The base arguments listed here are only one layer and are deliberately not presented as a complete runnable command. Check any nightly-image requirement and the model’s parsers before loading weights. A context declaration is a model limit, while batched-token and sequence settings control a serving workload.
Source: vllm-project · pinned document
What does the memory number mean?
The GB figure is the recipe’s declared planning minimum for the selected variant. It is not a site measurement, a universal peak allocation or a promise of maximum context. KV cache, auxiliary/draft models, image encoders, temporary workspace and active requests still require memory. Keep GB and GiB distinct, and use the actual artifact size and runtime allocation for a machine-specific budget.
Source: vllm-project · pinned document
What is needed to reproduce a deployment?
Save the model and conversion revisions, weight hashes, tokenizer/template, container or runtime digest, device count/topology and complete resolved launch. First check one short public request. For a subsequent measurement, fix input and output counts, concurrency, cache state, warmup, sampling, reasoning effort, repetitions and failures. The declarations on this page are source configuration facts; no throughput or quality outcome follows from them.
Source: vllm-project · pinned document
What does the source specify?
These declarations belong to the cited document. A planning minimum, model limit and measured runtime allocation are different quantities.
| Architecture | dense |
|---|---|
| Total parameters as counted by recipe | 16B |
| Active parameters as counted by recipe | 16B |
| Native context declaration (tokens) | Not specified |
| Model-wide minimum vLLM | 0.29.0 |
| Effective default-variant minimum vLLM | 0.29.0 |
| Default artifact | Qwen/Qwen-Image-2.1 |
| Default precision label | bf16 |
| Default planning minimum (GB; recipe declaration) | 40 |
| Default variant hardware allowlist | Not specified |
| Shared base arguments (incomplete launch) | [] |
| Declared compatible strategies | ["single_node_tp"] |
| Optional feature names | [] |
| Features selected by default | [] |
AI-assisted source reading and original editorial synthesis; no independent model execution.