-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Don't check overflow for bf16 data type #4512
Conversation
@hablb, thanks for the PR. While I understand restricting overflow checks to fp16 only, I don't see the benefit of providing a config option to enable overflow checks for bf16/fp32. Can you please explain the need for the config option? I think the restriction part is fine. |
43af495
to
75269d6
Compare
Thanks @tjruwase |
Always check for fp16 bf16 dynamic range is similar to fp32. don't check overflow by default. Co-authored-by: Olatunji Ruwase <[email protected]>
Dear @hablb ,Besides wasting computational resources, are there any other downsides to performing overflow checks on bf16 data types? Would performing overflow checks on bf16 data types cause any other bugs? |
No other downsides, however this check significant overhead as it reduces all gradients, communicates and synchronizes with the cpu. |
Always check for fp16 bf16 dynamic range is similar to fp32. don't check overflow by default. Co-authored-by: Olatunji Ruwase <[email protected]>
Always check for fp16
bf16 dynamic range is similar to fp32. don't check overflow by default.