fix: align JIT and class counters in compare timelines#55
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
1 participant
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.
Summary
JIT and Class Loading compare charts now keep counter values visible even when the two uploaded runs sampled at different seconds. The counter series advances to the latest observation at or before each shared frame, matching the forward-filled behavior that already made GC compare correctly.
Before this, GC could show both runs while JIT/Class only showed one run because counter metrics required exact timestamp matches on the shared compare timeline.
Verification
node --check frontend/public/compare-shared.jsnpm test -- --runInBand