I set torch, random, and numpy seeds, and my small fine-tune still moves run to run on a T4. Same recipe, same data — the weights at the same step differ between runs. For those of you who actually got reproducible fine-tunes: which flags mattered in practice — math attention backend only, a cuBLAS workspace config, cudnn.deterministic plus benchmark=False, or torch.use_deterministic_algorithms as a diagnostic? And what slowdown did you accept for it? I'm trying to find out which of these is the one that actually closes the gap, rather than turning them all on and hoping.
Backend
Beyond seeds: which determinism flags actually mattered for reproducible fine-tunes on a T4?
dev.to Machine Learning0 views
Source:https://dev.to/futurexindiafxgif/beyond-seeds-which-determinism-flags-actually-mattered-for-reproducible-fine-tunes-on-a-t4-3pcj
PreviousWhy Is Serving a Model Harder Than Training One?NextSystem design for physical AI: from drone footage to dispatched work at a port
Related posts
FiveM Script Database Migrations: What to Check Before You Install
0dev.to
The insurance edge case that breaks event-driven policy pipelines
0dev.to
The fix for an empty state isn't filling it
0dev.to UX
Five Things That Make Dependabot Painful for Terraform
0dev.to GitHub
Tracking Roblox player counts: what the public data actually gives you
0dev.to Data
Telegram gold signals this week: results to Oct 30
0dev.to Data