Papers › GShard: Scaling Giant Models with Conditional Computation and Automatic Sharding

GShard: Scaling Giant Models with Conditional Computation and Automatic Sharding

30 Jun 2020ICLR 2021 1arXiv:2006.16668archive 2025-07-28

Dmitry Lepikhin, HyoukJoong Lee, Yuanzhong Xu, Dehao Chen, Orhan Firat, Yanping Huang, Maxim Krikun, Noam Shazeer, Zhifeng Chen

Neural network scaling has been critical for improving the model quality in many real-world machine learning applications with vast amounts of training data and compute. Although this trend of scaling is affirmed to be a sure-fire approach for better model quality, there are challenges on the path such as the computation cost, ease of programming, and efficient implementation on parallel devices. GShard is a module composed of a set of lightweight annotation APIs and an extension to the XLA compiler. It provides an elegant way to express a wide range of parallel computation patterns with minimal changes to the existing model code. GShard enabled us to scale up multilingual neural machine translation Transformer model with Sparsely-Gated Mixture-of-Experts beyond 600 billion parameters using automatic sharding. We demonstrate that such a giant model can efficiently be trained on 2048 TPU v3 accelerators in 4 days to achieve far superior quality for translation from 100 languages to English compared to the prior art.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 10 code samples: 9 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 10: 9 ran (of which 2 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 9 samples from 1 repository, 8 ran (3 with no instrument failure; 5 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

facebookresearch/fairscale mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Megatron-LM: Training Multi-Billion Parameter Language Models Using Model Parallelism (arXiv:1909.08053; that paper's own run record: 12 ran (of which 2 constructed an object rather than computing a result; 7 with no instrument failure: 4 honoured, 0 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 35 unverified); nothing checks that they implement this paper's method. report
lucidrains/mixture-of-experts mentioned on GitHubpytorchSyntology: 9 samples, 8 ran (5 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

10 samples harvested: 9 ran (of which 2 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · violated contract
3ran · our draft was wrong
2ran; the contract check could not run
3ran
1unverified

Licence: 1 of the 10 samples is pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from lucidrains/mixture-of-experts. 1 sample is listed last, in a group without a repository. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 2 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

lucidrains/mixture-of-experts community (archive-listed) 9 samples, 8 ran (5 instrument-failed) · 1 unverified
Experts mixture_of_experts/mixture_of_experts.py ran · metamorphic tier: deterministic MIT (permissive) · 64ff1d169e3d5d58 · report fixture: returned Experts · level recorded 2026-09-22
GELU_ mixture_of_experts/mixture_of_experts.py ran fingerprinted MIT (permissive) · 2e0378380cff133f · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-24
Top2Gating mixture_of_experts/mixture_of_experts.py ran · metamorphic tier: deterministic MIT (permissive) · ed3578e7dda0ec22 · report fixture: returned Top2Gating · level recorded 2026-09-22
cumsum_exclusive mixture_of_experts/mixture_of_experts.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · 2458c57b5f0bfa20 · report fixture: signature t:Tensor/2/float, dim:int/0/int · returned Tensor · level recorded 2026-09-22
default in 430 papers mixture_of_experts/mixture_of_experts.py ran · our draft was wrong fingerprinted MIT (permissive) · dc9f7b2b73cab379 · report fixture: signature val:str/0/str, default_val:str/0/str · returned str · level recorded 2026-09-22
init_ in 12 papers mixture_of_experts/mixture_of_experts.py ran · our draft was wrong fingerprinted MIT (permissive) · 2aa1ea9fba4dce15 · report fixture: signature t:Tensor/2/float · returned Tensor · level recorded 2026-09-22
safe_one_hot mixture_of_experts/mixture_of_experts.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT (permissive) · d082003bd635a9de · report fixture: signature indexes:Tensor/1/int, max_length:int/0/int · returned Tensor · level recorded 2026-09-22
top1 mixture_of_experts/mixture_of_experts.py ran · our draft was wrong fingerprinted MIT (permissive) · 213bf6a36ff4baa6 · report fixture: signature t:Tensor/2/float · returned tuple · level recorded 2026-09-22
MoE in 10 papers mixture_of_experts/mixture_of_experts.py unverified MIT (permissive) · 928216f4fee84bf9 · report
Repository not located 1 sample, 1 ran (0 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
cast_tuple in 58 papers repository not located ran · violated contract fingerprinted licence of this copy not recorded · 369eced62e96d690 · report fixture: signature el:int/0/int · returned tuple · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for GShard (graph method: GShard). 10 bricks; individually on a fixture: 9 ran (of which 2 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

  1. MoE entry · level 0 · unverified · 928216f4fee84bf9
  2. Experts model · level 1 · ran · 64ff1d169e3d5d58
  3. Top2Gating model · level 1 · ran · ed3578e7dda0ec22
  4. default helper · level 1 · ran · our draft was wrong · dc9f7b2b73cab379
  5. cast_tuple helper · level 1 · ran · violated contract · 369eced62e96d690
  6. init_ helper · level 1 · ran · our draft was wrong · 2aa1ea9fba4dce15
  7. cumsum_exclusive helper · level 1 · ran; the contract check could not run (RAISES) · 2458c57b5f0bfa20
  8. safe_one_hot helper · level 1 · ran; the contract check could not run (RAISES) · d082003bd635a9de
  9. top1 helper · level 1 · ran · our draft was wrong · 213bf6a36ff4baa6
  10. GELU_ helper · level 1 · ran · 2e0378380cff133f

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2006.16668") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Machine TranslationMixture-of-ExpertsPlaying the Game of 2048Translation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Introduced by this paper: GShard

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutGShardLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerReLUResidual ConnectionSoftmaxTransformer

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