Optimize implementation of internal state change observers #1274
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.
Goal
Optimizes the implementation of the internal system used for notifying observers of state changes.
Changeset
This new solution avoids the performance disadvantages of the previous solution:
StateEvent
message is lazily created which avoids object instantiation if no observers are registeredBaseObservable
avoids creating aVector
by replacingupdate()
withonStateChange()
(this also grants additional type safety)BaseObservable
usesCopyOnWriteArrayList
which avoids the need for synchronization when adding/removing observers. This was seen as acceptable as observers will be added/removed very rarely, whereas the collection will be iterated over many timesThe remaining changes entail updating the rest of the code and the tests to use the new method signatures.
Testing
Updated existing unit test coverage and relied on existing tests.
Performance
Profiled app to confirm there was no performance regression, and also checked CI stats.