You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See #1513. The issue is that animating a color quickly fills up the color cache. We probably want to:
Cap the size of the cache and implement a policy like Least Frequently Used or segmented LRU
Change the caching policy when the color is animated (e.g. MRU, or don't cache at all. But if the animation repeats it could be helpful to have cached the values.)
Oh yeah, forgot about the color cache. Another approach is to maintain a frequency map of usage that is periodically periodically reset (never more than 10 entries or something). Then you only cache elements if they have multiple counts in the map.
See #1513. The issue is that animating a color quickly fills up the color cache. We probably want to:
Cap the size of the cache and implement a policy like Least Frequently Used or segmented LRU
Change the caching policy when the color is animated (e.g. MRU, or don't cache at all. But if the animation repeats it could be helpful to have cached the values.)
cc @sahrens@nicklockwood@vjeux for thoughts
—
Reply to this email directly or view it on GitHub.
See #1513. The issue is that animating a color quickly fills up the color cache. We probably want to:
cc @sahrens @nicklockwood @vjeux for thoughts
The text was updated successfully, but these errors were encountered: