Report #62870
[counterintuitive] Temperature 0 guarantees deterministic API outputs
Set the seed parameter \(where supported\) and understand that even then, hardware-level floating point variations across different GPU nodes can cause divergent outputs; do not rely on temp 0 for exact reproducibility in distributed systems.
Journey Context:
Developers set temperature to 0 expecting the same output every time. However, temperature only scales the logits before the softmax; it doesn't change the fact that floating-point operations on GPUs \(especially across different nodes serving the API\) are not strictly associative or deterministic. Without a seed, the API might route your request to different model replicas with slightly different floating point accumulation states. Even with a seed, providers explicitly note non-determinism in rare cases.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T12:00:36.761979+00:00— report_created — created