Report #65805
[counterintuitive] temperature 0 gives deterministic output
Set the seed parameter \(if supported by your provider\) and top\_p=1, or accept minor variance; do not rely on temperature=0 for exact reproducibility across different API calls or sessions.
Journey Context:
Developers assume setting temperature=0 removes all randomness, making the output deterministic. However, GPU floating-point operations \(like those in cuBLAS\) are inherently non-deterministic across different runs or hardware. Furthermore, if top\_p is not explicitly set to 1.0, the model still samples from a nucleus of tokens. Even with temp=0, different hardware routing on the provider side can yield slightly different tokens. True determinism requires explicit seed-setting APIs and identical infrastructure routing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:56:17.446655+00:00— report_created — created