-
Couldn't load subscription status.
- Fork 5.2k
[PERF] Add arm64 dynamic pgo runs #86014
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
Conversation
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsThis adds dynamic PGO arm64 runs to our regularly scheduled runs. It seems that everything should be properly configured just by setting the pgoRunType to DynamicPgo which then sets COMPlus_TieredPGO=1.
|
5f5c510 to
686e069
Compare
686e069 to
c9f03e6
Compare
8813628 to
ebb7c33
Compare
… well in performance-job.yml.
ebb7c33 to
261dd3c
Compare
|
Successful test (at least one of the logs for windows run succeeded) for arm64 dynamicPGO: https://dev.azure.com/dnceng/internal/_build/results?buildId=2177008&view=results |
|
Test run for Linux x64: https://dev.azure.com/dnceng/internal/_build/results?buildId=2177810&view=results |
|
All Perf pipeline tests resulted in passing data where this PR affected with the proper COMPLUS_Tiered...=1 being set. This also only impacts Perf Infrastructure so runtime pipeline failures are unrelated. Merging. |
This adds dynamic PGO arm64 runs to our regularly scheduled runs. It seems that everything should be properly configured just by setting the pgoRunType to DynamicPgo which then sets COMPlus_TieredPGO=1.
This is essentially a PR to get Linux PGO scenarios on par with the Windows ones from: 6c31866