Skip to content
← Performance Debugging & Benchmarking / 24
hardNewMistral AINVIDIA

A rollout replay reports a 1.25 probability ratio before any weight update. What would you check first?

An unchanged model appears to assign every sampled token 25% more probability. Reconstruct the sampling support, isolate the wrong denominator, and build a replay that distinguishes contract errors from numerical drift.

Updated Nov 2026 · Worked answers on inference mechanisms, with calculations, implementation details, and follow-up questions.

An unchanged model appears to assign every sampled token 25% more probability. Reconstruct the sampling support, isolate the wrong denominator, and build a replay that distinguishes contract errors from numerical drift.

10 answers per topic instead of 5, plus saved progress and bookmarks · costs nothingor unlock all 213 remaining answers · $25

Every worked answer and derivation in all 12 topics, every concept page, the full practice-test bank, and every code drill’s edge-case tests and reference solution.

6 months · One payment · No auto-renewal

UP NEXT ON YOUR JOURNEY
Next in this trackA load test says TTFT got faster when we doubled concurrency. What is wrong with the benchmark?Next in this trackAn FP8 KV cache run is 3.4% faster than the BF16 run. Design the A/B that decides whether to ship it.Next in this trackSame weights moved from a Transformers eval to vLLM; the score fell and some answers stop mid-sentence. Find the cause.
DISCUSSION · 0

Nobody has commented on this answer. Add a correction or another way to work it.