Performance regression on Lottie 3

[manolosavi]

Check these before submitting:

• The issue doesn't involve an Unsupported Feature
• This issue isn't related to another open issue

This issue is a:

• Non-Crashing Bug (Visual or otherwise)
• Crashing Bug
• Feature Request
• Regression (Something that once worked, but doesn't work anymore)

Which Version of Lottie are you using?

Lottie 3.0.4

What Platform are you on?

• MacOS
• iOS

What Language are you in?

• Swift
• Objective-C

Expected Behavior

Same or improved performance as previous versions of Lottie when running animations

Actual Behavior

Running an animation on a loop using Lottie 2.5.3 consumes around 16% CPU, while running that same animation on Lottie 3.0.4 consumes around 43%

Code Example

Animation JSON

Attached file

[buba447]

Duplicate of #832 and #828

[manolosavi]

@buba447 for what its worth we also tried installing off of master today and we didn't see any difference in CPU usage

[buba447]

I imagine there wouldnt be any difference. I havent had a chance to deep dive into the performance issues yet. The issues will be updated when I do though!

[alexbredy]

Same issue here. I am updating the currentProgress property of a Lottie animation on scrollViewDidScroll (creating a parallax offset) and performance dropped a lot since we migrated from v2 to v3. CPU consumption jumps making the frame rate drop.

[manolosavi]

@buba447 hi! just wanted to let you know that I just tried out version 3.1.2 and there are still issues in this version. The same screen shows CPU utilization of ~45% on 3.1.2 vs ~18% on 2.5.3, and the reported "energy impact" is "very high" vs "high".

[buba447]

Yeah I still haven't had a chance to work on the performance issues. They are caused by some limitations in the swift language cause by automatic memory management in structs. To fix the issue requires a pretty hefty refactor that I haven't had the resources to tackle. (Im working on lottie in my personal free time) We had to bump to 3.1 because of an API change. I will keep this thread updated when I get a chance to work on the performance issues.

…

On Aug 21, 2019, at 5:31 PM, manolo ***@***.***> wrote: @buba447 hi! just wanted to let you know that I just tried out version 3.1.2 and there are still issues in this version. The same screen shows CPU utilization of ~45% on 3.1.2 vs ~18% on 2.5.3, and the reported "energy impact" is "very high" vs "high". — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[manolosavi]

@buba447 thank you!

[Rapsssito]

Any news on this issue? I am experiencing 1 FPS frame drops with any animation on iOS, while they perform solid 60 FPS on Android (using lottie-react-native).

[paolo96]

I'm experiencing this issue too, any news? @buba447

[kirillsh]

+1
version 3.x is disappointing from performance point of view, have to downgrade to 2.5

[antonioallen]

Yeah, extremely poor performance CPU at 90% and memory when from 65mb to 1.2GB. Going to try downgrading as @kirillsh suggested.

[fila]

Having an issue with Memory usage while utilising the latest Lottie version (3.1.3). Tried to downgrade to 2.5.3, but this didn't actually help:

• the memory usage is the same (even went up a bit from 503.4 MB to 506.6 MB)
• the CPU usage did drop, but insignificantly: from avg. 7% to avg. 3%