Skip to content

Conversation

@mengluy0125
Copy link
Contributor

@mengluy0125 mengluy0125 commented Oct 3, 2024

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 3, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/137248

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 4141873 with merge base c83178d (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D63806598

@mengluy0125 mengluy0125 changed the title [PT2][Inductor][Reliablity] [PT2][Inductor][Reliablity] Fix PT2 latency regression on nanogpt Oct 3, 2024
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D63806598

…torch#137248)

Summary:


the runtime numeric check in the post grad D63438718 caused PT2 latency increase. We can find all regressions: https://fburl.com/fbdetect/2reizsu9


A failed example: https://www.internalfb.com/servicelab/experiment/4500528673/trial/4500826666

Test Plan:
```
buck2 run mode/opt //caffe2/benchmarks/dynamo/fb:torchbench_run_nanogpt_training -- -m nanogpt -t training
```


defaults-abs_latency-x1000: 51622


```
servicelab create benchmark_torchbench_run_nanogpt_training -d D63806598

```

https://www.internalfb.com/servicelab/experiment/4300563668/trial/4300883997

Differential Revision: D63806598
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D63806598

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2024

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the Stale label Dec 3, 2024
@github-actions github-actions bot closed this Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants