Add live scheduler timeline - #15
Merged
Merged
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
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.
What changed
Why
The task state is normally sampled between scheduler slices, so CPU-bound tasks often appear as
Readyeven though they are running fairly. A real scheduler trace makes execution order, frequency, and relative time visible without falsifying task state.Validation
spin_forever.wasmtasks: two live lanes, alternating slices, approximately 47% / 53% execution share1 fuel/ms: adaptive window expands to 40 seconds0 fuel/ms: status changes toFuel pausedwhile the prior window is retainedRuntime: OKnode --check main.jsbash -n build-browser.shgit diff --check-Wall -Wextra -Werror