Papers
Topics
Authors
Recent
Search
2000 character limit reached

Fully Sharded Expert Parallelism

Updated 4 July 2026
  • Fully Sharded Expert Parallel (FSEP) is a parallelization paradigm that shards MoE expert parameters across devices, allowing dynamic reconstruction via All-to-All communication.
  • It enables flexible expert re-layout and effective load balancing during both training and inference, improving throughput and reducing memory usage.
  • Variants like LAER-MoE, Expert Streaming, and MoEShard adapt the FSEP approach to different hardware setups, achieving significant speedups with minimal communication overhead.

Fully Sharded Expert Parallel (FSEP) denotes a set of Mixture-of-Experts (MoE) parallelization schemes in which expert parameters—and, in some formulations, token activations—are sharded across all participating devices or chiplets rather than bound monolithically to one device. In LAER-MoE, FSEP is a training paradigm that fully partitions each expert parameter by the number of devices and restores partial experts at expert granularity through All-to-All communication during training. In "Expert Streaming," FSEP, also called Fully Sharded Expert Data-Parallelism (FSE-DP), is a fine-grained parallelization paradigm for low-batch MoE inference on multi-chiplet accelerators. In MoEShard, FSEP is an inference strategy that decomposes each expert by a column-wise split of WiW_i and a row-wise split of WoW_o so that every GPU performs exactly 1P\tfrac1P of the expert’s total FLOPs, regardless of routing skew (Liu et al., 12 Feb 2026, Ma et al., 29 Mar 2026, Balmau et al., 11 Mar 2025).

1. Terminological scope and shared abstraction

Recent usage does not restrict FSEP to a single execution pattern. The term appears in distributed training, multi-chiplet low-batch inference, and multi-GPU inference, but the recurring structural idea is global expert sharding combined with runtime reconstruction, streaming, or aggregation.

Work Setting Defining mechanism
LAER-MoE MoE training Fully partitions each expert parameter by the number of devices and restores partial experts at expert granularity through All-to-All communication
Expert Streaming Low-batch MoE inference on multi-chiplet accelerators Shards both token activations and expert weights across all chiplets and streams micro-slices over D2D links
MoEShard Multi-GPU encoder-based MoE inference Column-wise split of WiW_i and row-wise split of WoW_o across PP GPUs

Taken together, these formulations suggest that FSEP is best understood as a sharding principle rather than a single fixed runtime. What remains constant is that expert state is globally partitioned; what varies is whether the system reconstructs full experts on demand, streams micro-slices along trajectories, or aggregates partial outputs after shard-local computation (Liu et al., 12 Feb 2026, Ma et al., 29 Mar 2026, Balmau et al., 11 Mar 2025).

2. Training-oriented FSEP in LAER-MoE

In LAER-MoE, the global symbols are NN for the number of devices, EE for the total number of experts, CC for expert-capacity per device, and Ψexpert\Psi_{\text{expert}} for the size of one expert. Every expert’s parameter tensor is fully sharded across all WoW_o0 devices, instead of binding each expert to a single device. Let

WoW_o1

be the flattened parameter vector of expert WoW_o2. FSEP splits WoW_o3 into WoW_o4 disjoint, equal-sized shards,

WoW_o5

where each shard WoW_o6 is stored on device WoW_o7 after the initial shard step. During a forward pass, each device WoW_o8 identifies a set of WoW_o9 experts it must invoke via the gating or routing mechanism; it then issues an All-to-All unshard so that, for each needed expert 1P\tfrac1P0, device 1P\tfrac1P1 collects the 1P\tfrac1P2 shards 1P\tfrac1P3 and locally reassembles

1P\tfrac1P4

Backward proceeds similarly: after computing gradients 1P\tfrac1P5, each device holds full 1P\tfrac1P6 for its 1P\tfrac1P7 experts; a second All-to-All reshard splits these gradients back into 1P\tfrac1P8 shards and scatter-reduces them so that each device 1P\tfrac1P9 adds WiW_i0 to its local shard’s gradient (Liu et al., 12 Feb 2026).

The architectural consequence is explicit in the paper: FSEP exposes the same memory benefits as FSDP, because each device only permanently stores WiW_i1 of every expert, while also enabling dynamic per-iteration expert-placement, since any device can choose any WiW_i2 experts to reconstruct. This dynamic placement is the basis for LAER-MoE’s load-adaptive expert re-layout during training.

3. Communication model, overlap conditions, and fine-grained scheduling

In LAER-MoE, each unshard and each reshard is a balanced WiW_i3-way All-to-All among the WiW_i4 devices. Per device, if it restores WiW_i5 full experts, it must send out WiW_i6 shards and receive WiW_i7 shards on each All-to-All, giving

WiW_i8

bytes per device per All-to-All. By contrast, in a traditional FSDP + EP split where EP group size is WiW_i9 and FSDP group size is WoW_o0 with WoW_o1 and WoW_o2, an FSDP AllGather on WoW_o3 experts costs

WoW_o4

The ratio tends to WoW_o5 as cluster size grows. The paper further states that these models imply that FSEP adds only WoW_o6 extra communication overhead but gains full re-layout flexibility (Liu et al., 12 Feb 2026).

Communication hiding is integral rather than incidental. FSEP interleaves or shadow-launches the All-to-All on a dedicated CUDA stream and overlaps forward unshard for layer WoW_o7 during expert compute of layer WoW_o8, while backward delays reshard of layer WoW_o9 until the next MoE layer’s backward compute. Under a bfloat16 SwiGLU MLP with hidden size PP0, intermediate PP1, top-PP2, and token count PP3 per device, the compute–comm overlap condition is

PP4

In practice on A100s and typical PP5, this holds comfortably, letting the communication be “free.” The fine-grained schedule uses four CUDA streams: Stream S0 for AttentionPP6 compute, Stream S1 for MLPPP7 expert compute and concurrently prefetch unshardPP8, Stream S2 for delayed gradient reshardPP9 scheduled at the start of backwardNN0 compute, and Stream S3 for token-dispatcher All-to-AllNN1. The stated effect is reduced idle gaps and channel contention compared to a single coarse communication phase (Liu et al., 12 Feb 2026).

4. Expert re-layout planning and load balancing

The principal benefit claimed for training-time FSEP is per-iteration freedom to choose exactly which NN2 experts each device reconstructs. LAER-MoE introduces binary placement variables NN3 indicating that device NN4 restores expert NN5, with NN6 for all NN7, and routing variables NN8 giving the number of tokens originally on device NN9 routed to expert EE0 but sent to device EE1, with EE2. Total iteration time is modeled as EE3, where

EE4

and

EE5

The joint integer program minimizes EE6 subject to the placement and routing constraints (Liu et al., 12 Feb 2026).

Because this is a large nonlinear IP, LAER-MoE splits it into two heuristics. The token dispatcher, Alg. LiteRouting, evenly splits EE7 among replicas of expert EE8 while preferring intra-node replicas to reduce cross-node traffic. The expert layout tuner, Alg. ExpertLayout, first decides replica counts expert_repEE9 by priority-queue, repeatedly assigning extra replicas to the expert with highest load/replicas until CC0; then places replicas greedily by sorting all CC1 in descending order and assigning each replica to the device with minimum current total load, balanced across nodes to respect topology; and finally evaluates a small set CC2 of schemes such as proportional, even, and random perturbations by computing CC3 via lite routing and picking the best. The overall greedy complexity is CC4, and in practice with CC5–CC6 it runs in CC7 ms per layer even at CC8 (Liu et al., 12 Feb 2026).

The reported outcome is a near-perfect balancing effect. In the case study, LAER-MoE keeps CC9 within Ψexpert\Psi_{\text{expert}}0 of perfect balance, whereas the baselines are Ψexpert\Psi_{\text{expert}}1–Ψexpert\Psi_{\text{expert}}2. This suggests that, within the planner’s objective, FSEP’s sharding is valuable less because it reduces asymptotic communication volume than because it makes expert placement a runtime decision rather than a static assignment.

5. Inference-oriented FSEP variants

For low-batch inference on multi-chiplet accelerators, "Expert Streaming" defines FSEP, or FSE-DP, as a fine-grained parallelization paradigm whose core ideas are to shard both token activations and expert weights across all chiplets, stream micro-slices of expert weights point-to-point over high-bandwidth D2D links, and dynamically schedule expert trajectories across chiplets to balance compute, on-chip storage, and communication. Let Ψexpert\Psi_{\text{expert}}3 be the number of chiplets, Ψexpert\Psi_{\text{expert}}4 the tokens-per-iteration aggregated across requests, Ψexpert\Psi_{\text{expert}}5 the experts per layer, and Ψexpert\Psi_{\text{expert}}6 the per-expert weight shape. Expert weights Ψexpert\Psi_{\text{expert}}7 are sliced into Ψexpert\Psi_{\text{expert}}8 equal expert-slices of size Ψexpert\Psi_{\text{expert}}9, and each expert-slice is further cut into WoW_o00 micro-slices of size

WoW_o01

At each timestep, each chiplet computes micro-slice WoW_o02 from expert WoW_o03 on its local token subset, simultaneously receives micro-slice WoW_o04 of WoW_o05 from the upstream chiplet via D2D and sends WoW_o06 downstream, and pre-loads the next micro-slice from DDR when buffer space is free. By choosing WoW_o07 so that WoW_o08, effective per-micro-slice latency is approximately WoW_o09. The dataflow is defined by five simple, hardware-embeddable rules governing receive-compute-forward, local fallback, buffer release at the final chiplet, opportunistic DDR fill, and optional prioritization of the chiplet with the largest available buffer (Ma et al., 29 Mar 2026).

The same work couples that dataflow to a dynamic expert trajectory scheduler. Experts are sorted by activation counts WoW_o10 and paired highest with lowest, so that a compute-bound hot expert overlaps with a communication-bound cold one. The scheduler maximizes WoW_o11 so no compute resources stay idle, balances hot and cold workloads by pairing, and can defer extreme cold experts through token buffering when a request has QoS slack. The paper states that FSEP achieves WoW_o12–WoW_o13 end-to-end latency speedup over EP or Hydra in low-batch WoW_o14–WoW_o15 tokensWoW_o16 MoE benchmarks and saves up to WoW_o17 percent on-chip memory (Ma et al., 29 Mar 2026).

MoEShard implements another inference-time FSEP for encoder-based MoE models in a multi-GPU setting. Each expert consists of two dense weight matrices, WoW_o18 and WoW_o19, and a classic expert invocation is

WoW_o20

With WoW_o21 GPUs, FSEP replaces each expert by WoW_o22 shards through a column-wise split of WoW_o23 and a row-wise split of WoW_o24:

WoW_o25

and

WoW_o26

Each GPU WoW_o27 loads exactly WoW_o28 for all experts. The paper states that every GPU performs exactly WoW_o29 of the expert’s total FLOPs, regardless of how many tokens that expert actually received. Communication remains a scatter/gather pattern, with per-layer per-GPU volume

WoW_o30

To reduce kernel-launch overhead, MoEShard uses expert-level fusion via MegaBlocks, and optionally stacks all experts into one larger block-sparse matrix so that all expert shards can be invoked in a single kernel launch (Balmau et al., 11 Mar 2025).

6. Empirical results, limitations, and recurrent misconceptions

On training workloads, LAER-MoE reports experiments on WoW_o31 A100 WoW_o32 GB with NVLink WoW_o33 GB/sWoW_o34 and InfiniBand WoW_o35 Gb/sWoW_o36 using Mixtral-8×7B, Mixtral-8×22B, and Qwen-8×7B in both e8k2 and e16k4 configurations on WikiText and C4. The reported end-to-end throughput is up to WoW_o37 speedup vs Megatron-LM, WoW_o38 vs FSDP+EP, and WoW_o39 vs FlexMoE. With auxiliary loss WoW_o40, LAER-MoE’s loss matches Megatron’s to WoW_o41 relative error, confirming no numerical drift. The case study reports that the All-to-All fraction drops from WoW_o42 to WoW_o43, a WoW_o44 reduction in dispatch/collect time, lite routing is WoW_o45 of iteration time, and disabling communication scheduling increases end-to-end time by WoW_o46 (Liu et al., 12 Feb 2026).

On inference workloads, the two FSEP variants emphasize different operating points. "Expert Streaming" is explicitly conditioned on multi-chiplet accelerators with high-bandwidth, low-latency D2D links, and states that it is not suited to monolithic accelerators lacking MIMD-style independent chiplet controls; micro-slice granularity must balance pipelining gain vs. control overhead, empirically WoW_o47–WoW_o48 micro-slices per expert slice; and token buffering trades per-request latency for throughput, so QoS parameters must be tuned to workload. MoEShard assumes WoW_o49 identical GPUs, all-to-all connected, such as NVLink; requires a high-bandwidth interconnect because of full token replication; assumes divisible dimensions, though padding or uneven splits can be used; and notes slight memory overhead for token buffers, though in practice negligible on modern GPUs (Ma et al., 29 Mar 2026, Balmau et al., 11 Mar 2025).

A recurrent misconception is that fully sharding experts necessarily implies prohibitive communication or token loss. The available results argue against both conclusions, though in different ways. LAER-MoE states that the communication ratio to FSDP AllGather tends to WoW_o50 as cluster size grows and that FSEP adds only WoW_o51 extra communication overhead while enabling flexible per-iteration re-layout (Liu et al., 12 Feb 2026). MoEShard states that it achieves perfect load balancing through tensor sharding of MoE experts, ensures full token retention, and does not rely on heuristic capacity factors or drop tokens; in its reported evaluation on Switch-Base encoder with T5 + 256 experts on BookCorpus using WoW_o52 NVIDIA A100 80 GB, per-layer forward latency falls from WoW_o53–WoW_o54 ms/layer in DeepSpeed to WoW_o55–WoW_o56 ms/layer in MoEShard, and TTFT speedup reaches WoW_o57 at WoW_o58 experts and remains above WoW_o59 up to WoW_o60 experts (Balmau et al., 11 Mar 2025).

These results suggest that the main significance of FSEP is not a single universal algorithmic improvement, but a reorganization of where MoE imbalance is handled. Static expert ownership is replaced by globally sharded expert state, and imbalance is then addressed through reconstruction, re-layout, micro-slice streaming, or fused shard-local computation, depending on the hardware and workload regime.

Topic to Video (Beta)

No one has generated a video about this topic yet.

Whiteboard

No one has generated a whiteboard explanation for this topic yet.

Follow Topic

Get notified by email when new papers are published related to Fully Sharded Expert Parallel (FSEP).