-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Split superpmi-diffs pipeline runs #84521
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak Issue DetailsRun tpdiffs and asmdiffs on separate Helix machines, in parallel, to improve overall job throughput.
|
/azp run runtime-coreclr superpmi-diffs |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Run tpdiffs and asmdiffs on separate Helix machines, in parallel, to improve overall job throughput.
dfa54d5
to
ef5b02e
Compare
Sample run: https://dev.azure.com/dnceng-public/public/_build/results?buildId=232648&view=results Note the elapsed time of 1:15 versus previous times of 2:15 to 2:30. |
@jakobbotsch PTAL |
Fixes #80718 (There are other ideas in that issue for additional parallelization work, but this is the "easy" fix that fixes the biggest time concern.) |
I created a diff type of "all" that is untested (and unused) -- just in case we might want it someday -- that would allow the previous behavior of doing both asmdiffs/tpdiff on the same machine. This turns out to have been easy to do and almost "falls out". |
Nice! |
Run tpdiffs and asmdiffs on separate Helix machines, in parallel, to improve overall job throughput.