Methods › General › Synchronous Pipeline Parallel › GPipe
GPipe
Introduced by Yanping Huang et al. in GPipe: Efficient Training of Giant Neural Networks using Pipeline Parallelism
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
GPipe is a distributed model parallel method for neural networks. With GPipe, each model can be specified as a sequence of layers, and consecutive groups of layers can be partitioned into cells. Each cell is then placed on a separate accelerator. Based on this partitioned setup, batch splitting is applied. A mini-batch of training examples is split into smaller micro-batches, then the execution of each set of micro-batches is pipelined over cells. Synchronous mini-batch gradient descent is applied for training, where gradients are accumulated across all micro-batches in a mini-batch and applied at the end of a mini-batch.
In Syntology harvested code stored, below machine verification (unverified_code; harvested), served level V1; retrieve with get_harvested_code_for_paper(arxiv_id='1811.06965'). Repositories: 13 listed of 13 in the graph, strongest link: mentioned on GitHub. The lookup matched a paper by its title, arXiv:1811.06965, not a method entry. This answer is about arXiv:1811.06965, the paper the archive credits with this method.
Origin paper of this answer, arXiv:1811.06965 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 20 ran (of which 0 constructed an object rather than computing a result; 19 with no instrument failure: 0 honoured, 0 violated, 19 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified (of 25 harvested samples) · 16 pointer-only (licence). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.
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.
What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).
Papers archive 2025-07-28
archive papers tagged: 7 · with a code link: 5 · where Syntology ran a sample: 1 (1 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 (1 of 7 tagged: 1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: papers 1 to 7 of 7, 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.
-
PipeOptim: Ensuring Effective 1F1B Schedule with Optimizer-Dependent Weight Prediction 1 Dec 2023 · 1 repository · arXiv:2312.00839
-
Hydra: A System for Large Multi-Model Deep Learning 16 Oct 2021 · 1 repository · arXiv:2110.08633
-
Group-based Interleaved Pipeline Parallelism for Large-scale DNN Training 29 Sep 2021 · 1 repository
-
Automatic Graph Partitioning for Very Large-scale Deep Learning 30 Mar 2021 · 0 repositories · arXiv:2103.16063
-
Analyzing the Performance of Graph Neural Networks with Pipe Parallelism 20 Dec 2020 · 0 repositories · arXiv:2012.10840
-
torchgpipe: On-the-fly Pipeline Parallelism for Training Giant Models 21 Apr 2020 · 3 repositories · arXiv:2004.09910
-
GPipe: Efficient Training of Giant Neural Networks using Pipeline Parallelism 16 Nov 2018 · 13 repositories · arXiv:1811.06965Syntology 20 ran (of which 0 constructed an object rather than computing a result; 19 with no instrument failure: 0 honoured, 0 violated, 19 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified (of 25 harvested samples) · 16 pointer-only (licence)
Tasks archive 2025-07-28
19 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.
Usage over time archive 2025-07-28
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
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