179 questions
No questions match those filters.
You're about to sign off on a large pre-training run. What's the actual checklist you walk through before submitting the job, beyond "the model architecture looks right"?
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 plansWork backward from the two ways a run gets wasted: it doesn’t fit the hardware, or it finishes and the result is quietly bad. On data, confirm exact and near-duplicate deduplication have both run (hash-based for exact matches, MinHash/LSH for near-duplicates), confirm a quality filter is actually in the pipeline — language identification, rule-based heuristics, a learned scorer — and, non-negotiably, confirm zero evaluation-benchmark contamination in the training corpus, because a contaminated run produces numbers you can’t trust regardless of anything else being right. Check total token count against a compute-optimal target: the ~20 tokens-per-parameter Chinchilla ratio is a floor, not a target, since production runs now go well past it because inference cost amortizes better against a smaller, longer-trained model.
On memory and parallelism, compute per-GPU memory for weights, gradients, and optimizer state given your parallelism degrees, keep it under roughly 85% of device HBM, and only escalate ZeRO sharding stage or add tensor and pipeline parallelism once that threshold is actually violated, not by default. For sequences past roughly 32K tokens, confirm context parallelism is configured, since KV memory during training scales quadratically with sequence length without it. Finally, name your dominant bottleneck — compute, memory, or inter-GPU bandwidth — and the first metric you’d watch, typically model FLOPs utilization for training, because if you can’t say what you’re bottlenecked on, you can’t say the configuration is actually right.