18How many spare GPUs, nodes, cables and transceivers do you hold for a 2,048-GPU fleet?▼mediumCoreWeaveMetaLambda Labs5 replies○ sign inEstimate replacement demand over replenishment time, then size for shortage risk and failure correlation. Distinguish shelf parts from runnable spare nodes.Open full answer →
36Transceivers are failing at three times the rate you budgeted. Find out why.▼hardMetaCoreWeaveNVIDIA4 replies◆ premiumConfirm the event definition and exposure, compare cohort rates, then test whether the cause follows a module, location or optical path.Open full answer →
19At 16,000 GPUs something fails every few hours. How do you choose the checkpoint interval, and what does the write have to look like?▼hardMetaAnthropicMicrosoft4 replies○ sign inBalance checkpoint pauses against lost work using job-level interruption data, while accounting for asynchronous durability lag.Open full answer →
01How do GPUs actually fail at fleet scale, how often, and which failures should the platform expect to handle every day?▼easy★ EssentialMetaCoreWeaveLambda4 repliesunlockedUse the Llama 3 interruption record without turning job interruptions into device lifetime, predictable failures or a universal spare percentage.Open full answer →
30Your fleet is replacing one percent of its GPUs every month. Is that normal, and how would you find out?▼expert★ EssentialMetaCoreWeaveMicrosoft4 replies◆ premiumDetermine what the replacement count measures, compare equivalent device exposure and investigate differences by cohort, location, age, software and policy. Job-interruption statistics cannot supply a hardware replacement baseline.Open full answer →