179 questions
No questions match those filters.
You're handed a compute budget and a target model size. Walk through how you'd actually assign data, tensor, pipeline, and — if the model is MoE — expert parallelism across the cluster.
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansStart from what’s true regardless of topology: tensor parallelism doesn’t consume batch size the way data and pipeline parallelism do, so it’s the right tool specifically for fitting a single layer in memory, and it should stay within a fast-interconnect domain — typically one NVLink node — because its all-reduce traffic degrades sharply once it crosses a slower inter-node fabric.
Pipeline parallelism comes next: it splits the model depth-wise across nodes, trading a bubble (idle time roughly proportional to (stages−1) divided by microbatch count) for the ability to scale past a single node without paying tensor parallelism’s cross-node tax; size the microbatch count to keep that bubble to a few percent. Data parallelism, usually ZeRO-sharded, fills whatever GPU budget remains and is what you scale to hit your target global batch size, capped by the critical batch size beyond which more parallelism stops helping training speed. For a dense model, that’s the whole picture: DP times TP times PP equals total GPUs.
For MoE, expert parallelism takes over tensor parallelism’s role inside the FFN block — route tokens to whichever GPU holds their assigned expert via all-to-all rather than sharding the matrix and all-reducing partial sums, set EP degree so each rank holds one expert, and note DP and EP typically share the same physical GPU grouping in practice. The discipline throughout is picking each axis for the specific constraint it relieves, never by default.