Include animation duration when computing cost/complexity of time remapping #2381
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.
Time remapping in the Core Animation rendering engine is expensive for large animations, since it requires manually interpolating each layer at each frame. #2286 (comment) added a complexity cap based on the number of layers, where if an animation had too many layers we would fall back to the main thread rendering engine.
#2330 has fewer layers than the previous cap, but is really long so still causes the app to hang while being initialized. Instead of only counting the number of layers, we should also consider the duration of the animation.