NodeValid

Published video-model weights, licences and hardware notes

Offloading discussed, or memory measured

Pyramid Flow discusses offloading and publishes no gigabyte figure anywhere. Cosmos Predict 2.5 publishes 32.54 GB of GPU VRAM with Ampere, Hopper and Blackwell named. The two ends of this column. As of 2026-09-22.

Pyramid Flow and Cosmos Predict 2.5 on the same columnNaming a memory technique without measuring it and measuring memory to two decimals are the widest two positions the hardware column holds.Pyramid FlowCosmos Predict 2.5Hardware, as each vendor statesitNo memory figure recorded32.54 GB of GPU VRAMThe detail published beside itOffloading is discussed without gigabytesAmpere, Hopper and Blackwell named assupportedResolution, from the same pages768p, with a 384p checkpoint720PA lever named, or a number published
Fig. 1 The vaguest and the most exact entries in one column, side by side.
What the repositories actually stateFilled where the repository states something, hollow where it does not. A blank is not an inference.What the repositories actually statePyramid FlowCosmos Predict 2.5Hardware, as each vendor states…Hardware, as each vendor states itHardware, as each vendor states it — Pyramid Flow: No memory figure recordedHardware, as each vendor states it — Cosmos Predict 2.5: 32.54 GB of GPU VRAMThe detail published beside itThe detail published beside it — Pyramid Flow: Offloading is discussed without gigabytesThe detail published beside it — Cosmos Predict 2.5: Ampere, Hopper and Blackwell named as supportedResolution, from the same pagesResolution, from the same pages — Pyramid Flow: 768p, with a 384p checkpointResolution, from the same pages — Cosmos Predict 2.5: 720PLength, from the same pagesLength, from the same pages — Pyramid Flow: 10 seconds at 768p, 5 at 384pLength, from the same pages — Cosmos Predict 2.5: A 5-second clip
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
Pyramid Flow and Cosmos Predict 2.5 on the hardware column, read from huggingface.co/rain1011 and huggingface.co/nvidia. Recorded 2026-09-22.
PointPyramid FlowCosmos Predict 2.5
Hardware, as each vendor states itNo memory figure recorded32.54 GB of GPU VRAM
The detail published beside itOffloading is discussed without gigabytesAmpere, Hopper and Blackwell named as supported
Resolution, from the same pages768p, with a 384p checkpoint720P
Length, from the same pages10 seconds at 768p, 5 at 384pA 5-second clip

Inclusion rule. Two families whose published values in this column lead to opposite decisions. A pair that happens to agree is not listed, because agreement is already visible on the column summary. Order. The column itself first, then its detail, then the columns that qualify it.

1Both cards were written by people who knew the answer

Nobody discusses offloading without having measured what it saves, and nobody publishes two decimal places without a script that reported them. The difference is what got written down.

That is worth saying plainly because the gap reads like a difference in rigour and is really a difference in audience: one card is for researchers, the other for deployment.

2What each release does document well

Pyramid Flow states ten seconds at 768p and five at 384p, both at 24 FPS, per checkpoint. Cosmos states 720P, 16FPS and five seconds with an exact parameter count.

Neither is a thin page. They are thorough about different columns, which is the normal condition in this register rather than an exception.

3The consequence for a reader with one card

One row can be checked against a specification sheet in under a minute. The other cannot be checked at all, because the card publishes no count either, so even unsafe arithmetic is unavailable.

The register records the absence and names the technique the card discusses. It does not estimate the gigabytes.

4Sources

Read from huggingface.co/rain1011 and huggingface.co/nvidia on 2026-09-22. Full entries: Pyramid Flow and Cosmos Predict 2.5. What this column is quoting is on hardware. Nearby pairs: 4GB against 60GB, Cards or gigabytes.