Run all Pytorch CodSpeed benchmarks on macro (bare-metal) runners (#4333) - #4333
Open
kinto0 wants to merge 1 commit into
Open
Run all Pytorch CodSpeed benchmarks on macro (bare-metal) runners (#4333)#4333kinto0 wants to merge 1 commit into
kinto0 wants to merge 1 commit into
Conversation
Contributor
|
@kinto0 has exported this pull request. If you are a Meta employee, you can view the originating Diff in D113490843. |
kinto0
force-pushed
the
export-D113490843
branch
from
July 30, 2026 23:14
e9ccbb7 to
ac49522
Compare
kinto0
added a commit
to kinto0/pyrefly
that referenced
this pull request
Jul 30, 2026
…cebook#4333) Summary: Splits the runner configuration out of the CodSpeed wiring diff (D112014630, which now keeps everything on `ubuntu-latest`) into this dedicated change: it moves `walltime` (PyTorch) — from `ubuntu-latest` to CodSpeed's dedicated `codspeed-macro` bare-metal runners. Bare-metal is what makes CodSpeed's wall-clock measurements trustworthy: on shared hosted runners, neighbor noise makes wall-clock data inconsistent, which CodSpeed warns about. Keeping both jobs on the same runner class also keeps the workflow uniform. Differential Revision: D113490843
…cebook#4333) Summary: Splits the runner configuration out of the CodSpeed wiring diff (D112014630, which now keeps everything on `ubuntu-latest`) into this dedicated change: it moves `walltime` (PyTorch) — from `ubuntu-latest` to CodSpeed's dedicated `codspeed-macro` bare-metal runners. Bare-metal is what makes CodSpeed's wall-clock measurements trustworthy: on shared hosted runners, neighbor noise makes wall-clock data inconsistent, which CodSpeed warns about. Keeping both jobs on the same runner class also keeps the workflow uniform. Differential Revision: D113490843
kinto0
force-pushed
the
export-D113490843
branch
from
July 31, 2026 17:57
ac49522 to
c375922
Compare
Unable to generate the flame graphsThe performance report has correctly been generated, but there was an internal error while generating the flame graphs for this run. We're working on fixing the issue. Feel free to contact us on Discord or at support@codspeed.io if the issue persists. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
Splits the runner configuration out of the CodSpeed wiring diff (D112014630, which now keeps everything on
ubuntu-latest) into this dedicated change: it moveswalltime(PyTorch) — fromubuntu-latestto CodSpeed's dedicatedcodspeed-macrobare-metal runners.Bare-metal is what makes CodSpeed's wall-clock measurements trustworthy: on shared hosted runners, neighbor noise makes wall-clock data inconsistent, which CodSpeed warns about. Keeping both jobs on the same runner class also keeps the workflow uniform.
Differential Revision: D113490843