Methods › General › Distributed Methods › PipeDream
PipeDream
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
PipeDream is an asynchronous pipeline parallel strategy for training large neural networks. It adds inter-batch pipelining to intra-batch parallelism to further improve parallel training throughput, helping to better overlap computation with communication and reduce the amount of communication when possible.
In Syntology repository known, no verified implementation (declared_code; repositories: 1 listed of 1 in the graph, strongest link: mentioned on GitHub). The lookup matched a paper by its title, arXiv:1806.03377, not a method entry. The archive credits no paper with an arXiv id for this method, so whether this answer (about arXiv:1806.03377) is about this method is not checked.
Origin paper of this answer, arXiv:1806.03377 (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: 5 · with a code link: 2 · 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 5 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 5 of 5, 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.
-
GraphPipe: Improving Performance and Scalability of DNN Training with Graph Pipeline Parallelism 24 Jun 2024 · 0 repositories · arXiv:2406.17145
-
PipeOptim: Ensuring Effective 1F1B Schedule with Optimizer-Dependent Weight Prediction 1 Dec 2023 · 1 repository · arXiv:2312.00839
-
Pipeline Parallelism for Inference on Heterogeneous Edge Computing 28 Oct 2021 · 0 repositories · arXiv:2110.14895
-
Group-based Interleaved Pipeline Parallelism for Large-scale DNN Training 29 Sep 2021 · 1 repository
-
LayerPipe: Accelerating Deep Neural Network Training by Intra-Layer and Inter-Layer Gradient Pipelining and Multiprocessor Scheduling 14 Aug 2021 · 0 repositories · arXiv:2108.06629
Tasks archive 2025-07-28
8 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.
| Task | Papers |
|---|---|
| Edge-computing | 1 |
| GPU | 1 |
| Image Classification | 1 |
| Machine Translation | 1 |
| Prediction | 1 |
| Scheduling | 1 |
| Sentiment Analysis | 1 |
| image-classification | 1 |
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