Zenaique

Which parallelism choice fits tight memory with fast interconnect?

MCQ·Medium·4.0 · 0·~1 min·Asked atAutodeskGraphcoreNVIDIA·Relevant atMeta
Attempt it
TL;DR

When memory is tight and interconnect is strong, FSDP or ZeRO-3 style sharding is usually the best first choice.

Memory aid
Sign in to see the mnemonic that makes this stick.
Easy to grasp

Imagine a group carrying heavy boxes up stairs. If each person carries a full copy of every box, everyone gets overloaded. A better plan is to split each box into parts so each person carries only a share, then combine when needed. FSDP and ZeRO-3 do this for model states across GPUs, which is why they help memory-bound training.

Concept explanation~2 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Interviewers ask about choosing a parallelism strategy for memory-bound training with good interconnect because this decision controls run quality, cost, and failure risk in real pretraining programs. A surface-level answer often repeats one slogan, but the actual decision lives in how assumptions, metrics, and constraints interact over time. In modern large-model development, teams cannot afford that gap. One planning mistake can burn weeks of cluster time and still leave weaker checkpoints.

This deep dive is structured as a practical walkthrough. First we build the mechanism and objective framing. Next we show where the popular shortcut breaks. Then we connect that to run-time telemetry, decision gates, and failure diagnostics. We close with deployment-facing consequences and a concrete numerical scenario. The goal is not trivia recall. The goal is to explain the concept in a way that sounds like someone who has operated a real training program and can justify tradeoffs under pressure.

Build the mechanism before the slogan

Mechanism first. Start with the core statement: State sharding distributes parameters, gradients, and optimizer states across devices. In practice, this means the question is never isolated from budget and objective context. A ratio, optimizer, masking rule, or parallelism choice only makes sense once you specify what is fixed and what can move. Teams that skip this framing often end up comparing unlike runs and then drawing false conclusions from noisy curves.

The right way to reason is to separate invariants from knobs. Invariants include hardware budget, objective type, and safety constraints. Knobs include model size, token budget, batch, sequence length, optimizer settings, and parallelism strategy. Once those are explicit, you can reason in cause and effect form rather than slogan form.

A good interview answer names this structure out loud: what is fixed, what is being changed, and what metric you optimize. That alone signals maturity because it prevents category errors.

A compact expression often used in this context is:

Replicated stateSharded state\text{Replicated state} \rightarrow \text{Sharded state}

You do not need to derive every constant during an interview. You do need to explain what the expression means operationally and what assumptions make it useful.

\text{Replicated state} \rightarrow \text{Sharded state}
Find the boundary where the shortcut fails
Run-time telemetry that makes decisions defensible
Production impact, risk, and mitigation
Interview delivery pattern for senior signals
Decision rubric and post-run review loop
Sign in to unlock the full deep dive.

Situations where this technique stops working.

Sign in to see when this approach fails.

2–4 min · Everything important, quickly.

Sign in to see the quick scan of the deep dive.

Real products, models, and research that use this idea.

  • Large pretraining stacks commonly use FSDP or ZeRO-3 to fit models that DDP replication cannot hold.
  • High-bandwidth GPU clusters are often tuned specifically to make sharded training efficient.
Sign in to see more production examples.

What an interviewer would ask next. Try answering before peeking at the approach.

QHow do you decide between FSDP and ZeRO-3 in practice?
A

Compare framework maturity, optimizer support, checkpoint format, and operational tooling.

2 more follow-ups an interviewer would ask next. Sign in to reveal them.

Red flags & common mistakes

The phrases that signal junior thinking. Click to expand.

Most common mistake

A frequent mistake is picking pure DDP even when memory replication is the primary bottleneck.

Sign in to see all red flags and common mistakes.

60 second bullets to scan on the way to the call.

  • Identify primary bottleneck

  • DDP replication limits

Sign in to unlock the revision sheet.

Primary sources. Browse if you want the original framing.

Similar questions

Same topic, related formats. Practice these next.

4 curated
Next question
Why does SFT struggle…
MCQ·Medium