

NVIDIA published the TensorRT LLM v1.3.0 GitHub release on November 20, listing additions to serving, memory management, precision formats and hardware support. The release notes explicitly label Rubin support as preview.
This is an inference-toolkit update, not the release of every model named in its compatibility list. A supported execution path also does not establish that a particular checkpoint fits a reader’s machine.
Cache and scheduling are part of the serving behavior
The release describes KV Cache Manager V2 as the default for most model families, additional cache-compression and storage options, and prefix-aware scheduling intended to avoid repeated work for shared prefixes. It also adds serving controls and parser options.
These choices can interact with request shape and available resources. A maximum context limit, a smaller stored weight format and a cache setting describe different parts of the system; none alone is a complete memory or throughput forecast.
Our analysis: check a supported configuration as a whole
Compatibility lists are most useful when read as combinations of model, GPU architecture, format and runtime feature. Treating any one supported item as proof that every combination works can turn an apparently simple update into a difficult deployment problem.
The preview label is another part of that decision. Teams should define which behavior needs validation for their workload and which limitations are acceptable before relying on a newly listed platform. We have not tested Rubin hardware or any supported configuration.
The release also lists an NVFP4 weight-only route through Marlin for Hopper and Ada Lovelace. Weight storage and execution precision should remain separate concepts when evaluating that option. We have not measured its memory use, speed or output quality.
Do not build a migration from stale command examples
The linked migration guide says PyTorch is the sole execution backend and lists removed TensorRT-engine APIs and build commands. It identifies retained legacy documents as cross-references. That guidance is context for upgraders, not evidence that every listed removal first happened in 1.3.
A familiar product name does not mean an older engine-building workflow remains current. Checking the versioned migration guide is more useful than copying a command solely because it appears in an older tutorial.
The repository has multiple license boundaries
The release license uses Apache-2.0 by default but explicitly places specified kernel directories under NVIDIA software terms and preserves third-party licenses. Describing the entire distribution simply as Apache-licensed would omit those exceptions.
Our repository profile links the source and records the qualification. No package, container, driver or model was installed, and no API compatibility or performance test was run for this report.
EXPLORE THE SOURCE
Projects in this story
GitHub repositories
- NVIDIA/TensorRT-LLM ↗View project details
Primary-source review and original editorial analysis. No software installation, model inference, API call, security validation or independent benchmark performed.


