Methods › General › Sharded Data Parallel Methods › ZeRO-Infinity

ZeRO-Infinity

2 papers tagged archive 2025-07-28

Introduced by Samyam Rajbhandari et al. in ZeRO-Infinity: Breaking the GPU Memory Wall for Extreme Scale Deep Learning

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

ZeRO-Infinity is a sharded data parallel system that extends ZeRO with new innovations in heterogeneous memory access called the infinity offload engine. This allows ZeRO-Infinity to support massive model sizes on limited GPU resources by exploiting CPU and NVMe memory simultaneously. In addition, ZeRO-Infinity also introduces a novel GPU memory optimization technique called memory-centric tiling to support extremely large individual layers that would otherwise not fit in GPU memory even one layer at a time.

PaperSource

In Syntology origin paper held, no code (paper_only). The lookup matched a paper by its title, arXiv:2104.07857, not a method entry. This answer is about arXiv:2104.07857, the paper the archive credits with this method.

Origin paper of this answer, arXiv:2104.07857 (its page on this site · its page on Syntology).

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

Papers archive 2025-07-28

archive papers tagged: 2 · with a code link: 0 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran: none of the 2 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 2 of 2, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

3 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
CPU2
GPU2
Large Language Model1

Usage over time archive 2025-07-28

Papers per year tagged with ZeRO-Infinity: 2021 to 2025, peak 1 1 0 2021: 1 paper 2021 2022: 0 papers 2022 2023: 0 papers 2023 2024: 0 papers 2024 2025: 1 paper 2025
Papers per year the archive tags with this method, by the paper's archive date (2 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Sharded Data Parallel MethodsData Parallel MethodsDistributed Methods

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections