Skip to content
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

[benchmarks] Fix AMP data-type. #6550

Merged
merged 2 commits into from
Feb 17, 2024
Merged

[benchmarks] Fix AMP data-type. #6550

merged 2 commits into from
Feb 17, 2024

Conversation

ysiraichi
Copy link
Collaborator

This PR fixes the behavior of AMP, aligning it to that of PyTorch HUD. Instead of setting a default data-type, we use the default one.

cc @miladm

@JackCaoG
Copy link
Collaborator

@yeounoh can you review this one? I don't remember why we set the default dtype.

@ysiraichi
Copy link
Collaborator Author

Truth is: it was my PR that set the default AMP data-type for the benchmarking scripts. The reason being that I hadn't understood the code (linked in the OP) correctly.

@ysiraichi
Copy link
Collaborator Author

I have reset the AMP data-types according to whatever is the default data type in torch.<device>.amp (or torch_xla.amp).

@ysiraichi ysiraichi merged commit 3d21839 into master Feb 17, 2024
18 checks passed
amithrm pushed a commit to amithrm/xla that referenced this pull request Mar 1, 2024
bhavya01 pushed a commit that referenced this pull request Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants