Perf(observableset): Remove extra clone operation on read #3993
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.
Code change checklist
/docs
. For new functionality, at leastAPI.md
should be updatedyarn mobx test:performance
)Context
within the observableset, on retriving
entries/keys/values
or during iteration, there is an extraArray.from
operation that is causing an unwanted copy of values within memory, the significance of extra operation is amplified when considering iterator helper methods where it would read the entire range of elements within the set instead of lazy evaluation, i.e:Set.prototype.entries().take(1)
, or any other case when the iterator is partially retrievedSet.prototype.entries().next()
.Benchmarks
Time
Use a macbook air M1 - 8GB model - plugged in, 1000 iterations
Memory
Mesuring the effect on memory when converting a large observableset to an array.