NVIDIA / NVIDIA/Model-Optimizer

Clarify recommended QAD configs for full-quality recovery in diffusers examples

Open
#1,812 5 comments 0 reactions 1 assignee View on GitHub

@ynankani is already working on this.

Since Jun 24, 2026.

question windows
Dominant language
Python
Stars
3.8k
Forks
604
Avg merge
2d 8h
Merged PRs (30d)
142

Description

Make sure you already checked the examples and documentation before submitting an issue.

How would you like to use ModelOpt

https://github.com/nvidia/model-optimizer/blob/main/examples/windows/diffusers/qad_example/README.md
I’m looking at the diffusers QAD example here:

examples/windows/diffusers/qad_example

The example config uses:

batch_size: 1
gradient_accumulation_steps: 4
steps: 300
FSDP num_processes: 8

So the effective batch size seems to be 1 × 4 × 8 = 32.

Could you clarify the recommended settings for a real production-quality QAD run, not just a smoke test?

Main questions:

What effective batch size is usually recommended for stable QAD quality recovery? Is 32 enough, or should we target 64 or higher?
Do you have any internal or public successful QAD examples for large Diffusers/DiT models such as LTX-2 or similar-size models? If yes, what batch size, steps, and learning rate were used?
For a full QAD recovery run on large diffusion models, roughly how many B200/B300 GPUs should users expect to need?
Is steps=300 only intended as a demo/smoke-test config, or has it been enough in real QAD recovery cases?

Who can help?
  • ?

System information

  • Container used (if applicable): ?
  • OS (e.g., Ubuntu 22.04, CentOS 7, Windows 10): ?
  • CPU architecture (x86_64, aarch64): ?
  • GPU name (e.g. H100, A100, L40S): ?
  • GPU memory size: ?
  • Number of GPUs: ?
  • Library versions (if applicable):
    • Python: ?
    • ModelOpt version or commit hash: ?
    • CUDA: ?
    • PyTorch: ?
    • Transformers: ?
    • TensorRT-LLM: ?
    • ONNXRuntime: ?
    • TensorRT: ?
  • Any other details that may help: ?

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.