A replica restarts and loads different weights than its siblings. How did that happen?

A mutable branch or local model directory can change what a restarted replica loads. Establish the actual artifact identity, separate disk evidence from loaded state, and make rollout and restart behavior reproducible.

Updated Sep 2026 · Learn how AI infrastructure works through explanations, worked examples and diagrams, then practise applying it to interview questions.

The full answer is part of Premium. A free account includes more answers in each topic, but does not unlock this one.

20 answers per topic instead of 10, plus saved progress and bookmarks · no cardor unlock all 316 remaining answers · ₹2,000 / $25

Work through the numbers

Change the assumptions in a free calculator, then explain what the result establishes and what still needs measurement.

The concepts behind this question

Use these concept explanations to review the ideas behind this question.

Advanced

📐 AI Systems Design🔒 Premium

Evaluation and Data Pipeline InfrastructureData pipelines prepare traceable training inputs; evaluation pipelines compare model behavior. Both need versioned inputs, reproducible execution and useful failure reporting.

Foundational

🧮 Open Weights & Serving Engines

Serving Benchmarks That Do Not LieDesign reproducible serving experiments with realistic arrivals, cache state and failure accounting. Interpret latency-qualified throughput and conditional per-rank bounds without turning optimistic kernel estimates into production capacity.

Foundational

🧮 Open Weights & Serving Engines

Capacity Planning for Open-Weights FleetsMatch forecast traffic to a measured replica operating envelope, then check failure domains, rollout capacity, readiness time and cost. Output tokens alone omit prompt work and live state; total parameter count alone does not determine a replica's throughput.

Foundational

🧮 Open Weights & Serving Engines

Open-Weights Models of 2026Compare current Chinese open-weight models by the artifact you can deploy: weight bytes, attention state, supported execution paths, and evaluation conditions. A dated guide to GLM, Kimi, DeepSeek, Qwen, and MiniMax, with worked sizing checks that separate parameter counts from GPU capacity.

Explore the full curriculum →

UP NEXT ON YOUR JOURNEY

Next in this trackYou must serve a frontier open-weights model on non-NVIDIA accelerators. Plan it.Next in this trackYour model's weights fit in GPU memory, but the engine cannot load them. How do you inspect the model package?Next in this trackConvert an open-weight checkpoint to GGUF for an edge deployment and prove the conversion is usable

FEDITOR'S NOTE

Scored on verifying loaded artifact identity, conditional branch/cache behavior, immutable manifests, integrity and retention controls, and reliable request attribution without unsupported failure-rate forecasts.

DISCUSSION · 0

No comments yet — be the first to share your approach.