[release/10.0] Fix YieldProcessorMeasurement running continuously due to timestamp truncation #122317
Conversation
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
Co-authored-by: jkotas <[email protected]>
Co-authored-by: agocke <[email protected]>
jkotas
approved these changes
Dec 9, 2025
Contributor
|
Tagging subscribers to this area: @mangod9 |
Member
|
/ba-g Know issue timeout |
This was referenced Dec 10, 2025
Open
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.
Backport of #122293 to release/10.0
/cc @agocke @copilot
The background process responsible for periodic updates of processor yield instruction costs consumes 100% of a single core on a machine with 50+ day uptime or non-standard OS timer configuration.
Customer Impact
Regression
Testing
Standard test pass, no testing specific to the fix - the bug requires machine with 50 day uptime to test
Risk
Low.