Update stats when unparking worker in multi-threaded runtime #6131
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.
Fixes #6129
I am not an expert on the runtime implementation, but looking at the code it seems like we should reset the start time for processing scheduled tasks when the worker thread unparks. Otherwise it only happens occasionally when calling
Context::maintenance
, which is why the worker busy duration metrics were getting so large.Using the following program:
Before
After