Add TieredPGO_InstrumentOnlyHotCode=0 to tier0 jobs#1765
Merged
Conversation
Member
|
Lesson: we should keep setting the values even when they are the default. |
Contributor
Author
|
Yep, but in this case |
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
2 participants
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.
We recently merged dotnet/runtime#70941 to runtime
It means that
pgo=tier0-instrumentedjob no longer measures instrumented code and TieredPGO_InstrumentOnlyHotCode=0 should be added to bring it back.cc @sebastienros