Consensus with a reservation: TensorRT-LLM is recommended only when you own the hardware and can absorb the build and operational complexity, and even enthusiasts concede the complexity

Two practitioner sources, four years apart, agree on the shape and differ on the tone. In 2023 a commenter in the launch thread leads with the gating friction: TensorRT-LLM at launch required that 'you must be registered in the NVIDIA Developer Program.' In r/LocalLLaMA a commenter argues flatly for the stack: 'vLLM and others are great but TensorRT-LLM is king... Combine it with the tensorrt_llm backend in Triton Inference Server and it blows anything else away: This is what most big commercial providers are using on their backends.' The same commenter immediately concedes the cost: 'Problem is it's all EXTREMELY complex.' And the industry answer that followed is blunter still: vLLM 'feels less professional but it's ez to setup.'

The condition attached to the recommendation is control of the hardware. TensorRT-LLM's cost is a build-time engine-specific step and a version-coupled upgrade path, so it only pays when the hardware is fixed and the workload is steady. The corpus does not record it being recommended to anyone who is iterating on hardware or on models.

Recommend it only for a fixed NVIDIA deployment with a stable model and a steady request rate, and staff the Triton integration as a real ongoing cost. For anyone still choosing hardware or changing models weekly, the corpus says vLLM or SGLang instead.

One hard, dated counter-example on consumer-class NVIDIA: the SM120 RTX PRO 6000 benchmark lists TensorRT-LLM as 'N/A - Doesn't support the arch'. So even inside the TensorRT-LLM camp the build-step recommendation silently assumes datacenter parts.