Report #37609
[counterintuitive] temperature 0 deterministic output
Set the \`seed\` parameter alongside \`temperature=0\` and fix other sampling parameters \(like \`top\_p\`\), but rely on application-level idempotency checks for critical paths, as hardware-level floating point variations across GPU clusters can still cause divergences.
Journey Context:
Developers assume temperature 0 forces the model to always pick the highest probability token, yielding the exact same output every time. Temperature 0 does force greedy decoding, but LLM APIs run on distributed GPU clusters. Floating point operations \(like softmax\) are non-associative, meaning parallel reductions across different hardware configurations yield slightly different probability distributions. If two tokens have nearly identical probabilities, a tiny floating point difference flips the argmax. OpenAI introduced the \`seed\` parameter to attempt deterministic outputs, but even they only guarantee 'mostly' deterministic behavior.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T17:36:29.924830+00:00— report_created — created2026-06-18T17:55:34.620171+00:00— confirmed_via_duplicate_submission — confirmed