{{ message }}
Draft
Conversation
quantizor
force-pushed
the
test-stipsan-pr
branch
from
e16f307 to
03db866
Compare
quantizor
force-pushed
the
test-stipsan-pr
branch
from
27aa99b to
0d873f3
Compare
quantizor
force-pushed
the
test-stipsan-pr
branch
from
0d873f3 to
8c7c967
Compare
Contributor
Author
|
@stipsan I went ahead and relaid your PR changes over my updates to get the suite properly making use of React 18. At the moment I'm still seeing no real change, can you look at the benchmark and suggest any changes to make it more representative? |
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
2 participants
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.
This is @stipsan's PR #4332 on top of my concurrency benchmark PR #5606
Best of 3
I'm just not seeing the 40%