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.

Sign up for GitHub

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

Jump to bottom

Optim Perf Signal Detected by TorchBench CI on '4e30fa82315208dcd38fa16a0ed9851fa8e98bc9' #1958

Closed
github-actions bot opened this issue Oct 4, 2023 · 1 comment
Closed

Optim Perf Signal Detected by TorchBench CI on '4e30fa82315208dcd38fa16a0ed9851fa8e98bc9' #1958

github-actions bot opened this issue Oct 4, 2023 · 1 comment
Labels
torchbench-perf-report

Comments

@github-actions
Copy link

github-actions bot commented Oct 4, 2023

TorchBench CI has detected a performance signal or runtime regression.

Base PyTorch commit: 4dae8b49630d2784f6a5d8726db30923e2d1e077

Affected PyTorch commit: 4e30fa82315208dcd38fa16a0ed9851fa8e98bc9

Affected Tests:

  • mobilenet_v3_large, Rprop, cuda, default: +58.95230%
  • detectron2_maskrcnn, Adam, cuda, differentiable: +44.64110%
  • shufflenet_v2_x1_0, Adagrad, cuda, no_foreach: -34.88800%

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/6401389857

cc @janeyx99
@janeyx99
Copy link
Contributor

conglomerating noise in #1988

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
torchbench-perf-report
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@janeyx99