Repository navigation
Benchmarks rerun on 0.2.2 - #9
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Reruns the benchmarks on the released 0.2.2, so the results page names the release and shows the smaller hook bundles:
useSmoothText4.7 kB and VueuseSmoothStream4.6 kB gzipped, down from 8.2 kB.The pacing results are identical to 0.2.1, as expected, since pacing did not change. The browser numbers moved within the usual run-to-run spread of a real-time replay. The first run of the browser part overlapped with an npm install on the same machine and showed long tasks on the reveal row, so it was run again with nothing else going on; this PR has the second run. In it the long stream logs one or two long tasks in the Markdown rows, including rendering as received, which points at the machine rather than at pacing.