AIPerf stage 8: qualify all TRTMC text-to-video models #1675

Request type

New capability

Problem and use case

Video generation needs asynchronous completion and real output artifacts; a successful job-creation response alone does not qualify native video inference.

Proposed outcome

Qualify all supported models in this group for one text-to-video generation workload through the existing native serving entrypoint.

• Workload: One prompt produces one clip at fixed resolution, frame count, FPS, and steps.
• Client / endpoint: AIPerf video_generation; POST /v1/videos, then job-status polling.
• Rollout / prerequisites: Model-group rollout after stage 7.

Public CI hardware failures — owner-approved handling for stages 5–8

Keep existing model contracts, references, numerical thresholds, test eligibility and repository merge-gate rules unchanged. If an in-scope model fails non-required public CI due to OOM or a demonstrated hardware limitation, execute the affected unchanged correctness case locally on capable hardware, retain a non-skipped passing result, and document the public failure and local verification in the PR. Merge only once the unchanged required merge checks pass on the current head and the PR otherwise satisfies the repository rules. A numerical/model-correctness failure is not a hardware exception. Do not add test exclusions or manufacture a passing public result. Deliver stages 5, 6, 7 and 8 sequentially, starting each implementation after the previous stage merges.

Existing-model scope — owner clarification

This epic integrates AIPerf with models and model specs already supported on upstream main. “Whole group” means every existing model/spec for this workload, rather than adding checkpoints that an architecture might also support.

• Reuse existing checkpoint identities, normal full-model profiles/manifests, build settings, references and correctness thresholds. Do not add model families, checkpoints, model specs/manifests, precision/parallel variants or new numerical gates to enlarge the group.
• HTTP/media adapters, AIPerf input/workload configuration and regression fixes needed for existing models are in scope. Keep model semantics family-owned and existing correctness criteria unchanged.
• Missing full-model implementations or native audio/video capabilities are recorded as unsupported/outside this integration. Do not implement a new encoder, model graph, temporal path or native Task to fill the inventory. L0/partial profiles do not require full-model onboarding in this epic.
• Refresh against current main only to include independently existing supported specs. Architectural compatibility, model cards and upstream model availability do not establish an in-scope TRTMC model.

Group-wide scope and completion (revised)

Cover every TRTMC-supported checkpoint in this model group for the workload below, not just one pilot. Refresh the inventory against github/main at implementation and before completion. Use family-owned manifests, actual build/runtime behavior, and public Task capabilities together; a model name, broad support declaration, or an inherited C++ interface alone does not establish the checkpoint's supported workload.

Use one normal full-model profile per distinct checkpoint and workload. Record all additional precision/quantization/TP/CP variants separately; do not count variants as extra models or claim untested configurations. L0/partial/random/regression smoke profiles do not establish full-model coverage. Checkpoints with only partial implementation remain explicit gaps, not silent omissions. Only independently existing supported specs on main join the refreshed inventory; do not add models or specs as part of this integration.

• Publish the exhaustive per-checkpoint inventory with checkpoint/profile/revision, native Task, supported controls, and any explicit capability gap; reconcile it with current main before closing.
• Every supported checkpoint passes its unchanged owning-family correctness criteria on the exact served bundle, followed by a real published pip-installed AIPerf run through trtmc-server for this one workload.
• Check meaningful complete output contents and native/HTTP identity for every model, with separately marked warmup, failures, client/Task timing, and workload-appropriate throughput.
• Publish a result row and reproducible command for every checkpoint. A pilot, source-only check, HTTP fixture, skipped test, unrun model, unsupported adapter, or unresolved failure cannot close this group-wide task.
• Preserve family ownership and existing quality criteria; fix real defects without introducing model behavior in shared serving code or relaxing gates.

Implementation scope:

1. Reuse asynchronous job and artifact mechanics while connecting to actual native generated-frame output.
2. Expose real completed artifacts, terminal job errors, and cleanup; document status/polling and artifact lifetime.
3. Record actual frames, dimensions, FPS, duration, steps, seed, and effective precision; retain family-owned video semantics and evaluation.

Acceptance criteria for every model in the group:

• Generated clips satisfy the unchanged family video validity/quality contract and requested supported configuration.
• A real pip-installed AIPerf run completes jobs, retrieves valid artifacts, and records failures rather than losing unfinished jobs.
• Report client job-completion latency separately from Task-call time and state polling cadence; measured work is explicit.
• Reuse existing serving/qualification mechanics; keep all model semantics, orchestration, and correctness family-owned, with capability-based Task dispatch.
• Account for inputs, outputs/artifacts, failures, and warmup by request identity. Keep client end-to-end latency separate from public_task_call_wall; exclude build/load/startup/warmup from steady-state timing.
• Record tested package versions, checkpoint/profile, actual bundle, dataset, endpoint/mode, hardware, effective precision, settings, commands, and public evidence. Distinguish planned, implemented, family-validated, and AIPerf-qualified status.
• Provide one concise reproducible example using published pip-installed AIPerf and links to existing build guidance; an AIPerf source checkout is not a runtime dependency.

Model and target details

Inventory baseline: TRTMC fd79ad26ca71a11b3ec086a7daaaead03e6c933f. Candidate models/profiles for this group:

Use one text-to-video workload across every supported video generator. The eligible existing full-model candidates are MiniMax-H3, Wan2.2-TI2V-5B and Wan2.1-T2V-1.3B. Cosmos3-Nano and LTX-Video have only partial/L0 profiles in this inventory: record them as excluded diagnostics, without creating full-model specs or implementations. Their missing full-model capability does not block qualification of the three existing full-model candidates. Wan2.2 TI2V belongs here for its actual text-to-video mode; image-to-video remains a separate workload.

Use the public native Task runtime path. Record the actual supported target GPU and software stack during implementation/qualification; no new hardware validation or benchmark is claimed by this planning issue. Keep existing numerical criteria unchanged.

Alternatives considered

Reuse apps/perf_serving protocol/media/recording mechanics and apps/aiperf_qual qualification instead of adding a third server or benchmark harness. Deliver this stage on its own short-lived branch from current github/main.

Follow-ups outside this initial stage: Image-to-video and other clip configurations are separate workloads.

Additional context

• Parent epic: Epic: expand TRTMC AIPerf model and workload coverage #1667
• Pilot profile
• AIPerf docs/tutorials/sglang-video-generation.md
• Native server
• Existing qualification harness

Research baseline: TRTMC 0bccb5e93af0e5ad346aaf44e404396f54b2e7de and AIPerf e1daadd10faa395100384358131d784d6858c5ae; published AIPerf 0.13.0. Recheck the tested published version and native capabilities when implementing. Existing source/fixtures/reference-only runs do not establish end-to-end TRTMC qualification. Keep internal logs, artifacts, and runner details private.

Submission checks

• I searched open and closed issues and found no duplicate request.
• I removed secrets, private/internal evidence, personal paths, and restricted artifacts.

Group completion policy revised at the owner's request: all supported checkpoints in this group must be accounted for and qualified; one successful pilot is insufficient. Existing pilot results are retained as historical evidence.

Stage 8 completion

Complete in PR #1802, squash merge 61d2402f61e77238b250729ecace9ac13d038df7. All three existing full text-to-video checkpoints passed the unchanged original owning-family cases on the exact served bundles and real published AIPerf 0.13.0 qualification on 33cfdae11cc80597c694b14485b01bc01943c441: nine complete clips, 786 frames verified, zero client errors, complete native/HTTP identity, original reference criteria and visual review passed. The PR publishes every checkpoint/pin/profile, existing variant and partial gap, original full settings, commands, polling cadence, client/Task timing and measured clip throughput.

The required sanitized internal gate passed on that exact head before a normal squash merge. Stable Community CI and CodeRabbit passed; both review conversations are resolved. Optional experimental Dev CI was still pending at merge and is not counted as a passing check. No model specs, family/core contracts, references, numerical thresholds, test eligibility or merge rules changed. Cosmos3-Nano and LTX-Video remain explicit partial/L0-only gaps under the existing-model boundary.