Performance: store effects in array instead of linked list #253
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.
Mirror of facebook/react#35370
Original author: romgrk
Summary
Considering that effects are only appended (the list of effects is never mutated in the middle),
Arrayseems like a better fit because it has a better cache locality, and it creates less memory allocations so there's less pressure on the GC.How did you test this change?
I have tested various benchmarks we have in Base UI and they've shown a fairly small but consistent improvement across the board. I've also spin up this benchmark that puts an extreme focus on effects to illustrate clearly the improvement. The average runtime is consistently lower, but interestingly the standard deviation is also consistently lower, which probably indicates that the garbage collector is doing less pauses (due to the fewer memory allocations).
Before:


After: