How to quantify the performance difference between rendering an image and a spine

Announcements
1

The reason is that the planner requires the implementation of an interface, which normally has about 20 interactive objects.

One solution is to make them into spine animations, load them directly into the interface, and play the actions when interaction is needed.
Another solution is to make them into spine animations and switch to a static image in standby mode. In the normal standby mode, the static image is displayed, and when interaction is required, the spine is loaded and the actions are played, and then the static image is switched back to after the playback is completed.

The first one is very convenient and easy to maintain, but the disadvantage is that too many spines may affect performance.
The second one is easy to batch, but the disadvantage is that it is very troublesome and the extra cutting will affect the package size.

Considering the difficulty of iteration, I definitely prefer the first option, but the planner asked me a question: How much performance overhead can the second option save? How much impact on frame rate can it reduce? How much heat generation can it reduce?

I didn’t know how to answer this question. Can anyone please tell me how to quantify the impact of these two situations on performance?

3 Likes
2

Find some test images, test the spine, put them up, and make sure they can’t be batched together. Try it. No need for too difficult logic, just display them directly. As long as the number is enough, it’s fine.

3

Yes, then open a performance dog to monitor the phone for 1 hour to see the changes in heat generation and battery level.

4

Of course, both are required. A picture and a spine fixed-frame animation. When interactive, hide the picture, show the spine, and play the animation; when normal, hide the spine and show the picture. As long as the spine is not displayed, it will not be rendered, and there is no performance pressure.

5

So what if the planner says to add a standby animation? And why would the planner ask about performance optimization?

6

Planning knows nothing about technology

7

Use rt when not moving. This solution meets all the advantages you want.

8

100 static images → open the lower left corner debug screenshot 1
100 spines → open the lower left corner debug screenshot 2