Closed github-actions[bot] closed 1 year ago
Some things, like attention_is_all_you_need_pytorch, Rprop, cuda, (pt2) maximize: +32.44805% llama BERT Adam no_foreach
are gradually increasing.
Also note that we have 217 total regressions (173 slowdowns) and 150 of them are pt2 related, so I'm guessing tracing is a culprit.
Closing this, but will keep observing trends
TorchBench CI has detected a performance signal or runtime regression.
Base PyTorch commit: 1a3d3669efa55e3360060c9b81f87900ae0c906c
Affected PyTorch commit: f3e13d956729d4fa9ce35dca5beed588c914797d
Affected Tests:
Tests that were no longer run on affected commit:
Tests that were newly added on affected commit:
Runtime regressions found? No runtime errors were found in the new benchmarks run--you are all good there!
GitHub workflow that triggered this issue: https://github.com/pytorch/benchmark/actions/runs/4987743943
cc @janeyx99