NVIDIA / NVIDIA/TensorRT-LLM

[Feature]: Add offloading support to visual_gen to reduce GPU memory usage

Open
#13,893 1 comment 0 reactions 1 assignee View on GitHub

@laikhtewari is already working on this.

Since May 8, 2026.

feature request VisualGen
Dominant language
Python
Stars
14.7k
Forks
2.8k
Avg merge
2d 23h
Merged PRs (30d)
489

Description

🚀 The feature, motivation and pitch

Feature request

I would like to add offloading support to tensorrt_llm/_torch/visual_gen.

The goal is to reduce peak GPU memory usage by allowing selected parts of visual generation pipelines, such as model components, auxiliary modules, or guardrails, to be offloaded when they are not actively needed during generation.

Motivation

This would help support more memory-heavy visual generation workloads on a wider range of GPUs.

In particular, it would be useful for:

  • GPUs with limited VRAM, including consumer/workstation GPUs
  • larger visual generation models
  • longer video generation
  • multi-view generation
  • pipelines that include extra components such as safety or guardrail models

Initial experiments suggest that offloading can significantly reduce peak GPU memory usage with limited latency overhead.

Proposal

Add a general offloading mechanism to visual_gen that can be configured by users and reused across visual generation models, rather than relying on model-specific pipeline changes.

I would be interested in contributing an initial implementation and would appreciate guidance on the preferred design/API for making this upstreamable.

Alternatives

No response

Additional context

No response

Before submitting a new issue...
  • Make sure you already searched for relevant issues, and checked the documentation and examples for answers to frequently asked questions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.