
The RTX Pro 6000 has two matmul engines, and vLLM was only using one of them when I ran Qwen3.6 27B NVFP4 Marlin is nice for decoding, but CUTLASS is 3.5x faster processing large token prompts. For some reason, vLLM ran Marlin for both, because NVIDIA's checkpoint files mislabel what the model can actually do. Fable 5 found out about all this and wrote a vLLM plugin that looks at the batch size and picks the right engine per call. Results is almost 2x increase in prefill at all context lengths:





















