Can you shortly tell us which rotation item you are using in your code and what your use-case is?
Some ideas that just came to my mind (these do not only apply to images but to all graphical components in your QML tree):
- If you don’t need the updated property values for each frame you can give RotationAnimator a try, in comparison to Animation components the Animator only updates the rendering but not the property values on each frame
- The rotation calculation itself is a CPU-intensive task as it has to calculate the new frames and rendering for each step. Depending on your use-case, a common work-around for that (for example for an activity spinner/indicator) is to create the rotated image frames outside of your QML projects as separate images and use a sprite animation for displaying the individual frames. This produces a small memory overhead but saves tons of rotation calculations.