-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pretraining loss explosion #554
Comments
My loss also exploded on an initial attempt with 8 A100 instance. I disabled flash attention and that seems to have fixed it, though it is much slower. |
@mattgorb @HarrisonUnifyAI I have not changed the default settings, other than the seed. (doing ddp on 8GPUs) |
I had similar results for training on 8xA100-SXM4-40GB. The validation loss graph is below. I changed the micro batch size to fit into GPU memory 64 → 16. To keep the total batch size, I increased accumulation steps:
I ran training three times with the same parameters. Training collapsed all three times, but the timing was different. |
I have been trying to get this repo working for several months, but my loss keeps exploding between 30k and 100k iterations.
I have tried many things:
Turn flash attention off ( based on this issue: #524)
Using fp16 (based in this: #468)
Using GPT-4 tokenizer (based on #468)
At first the loss was going back up to about 8-10, now it is just going to NaN with fp16.
I have also tinkered with other setting such as gradient clipping, learning rate, etc. I keep my configuration at roughly 500k batch size.
I am lost on what to try next. Did anyone else fix this issue?
I have gotten GPT-2 Small down to about 3.0 loss.
The text was updated successfully, but these errors were encountered: