in case you are driving a heavily animated GUI on a large display, the CPU load and the necessary memory bandwidth is high. You already did some measurements and the results sounds reasonable.
The big advantage of every Embedded Wizard GUI application is the cooperative model of every main loop. This means, you can give as much CPU time to the GUI processing as you want.
In case you are using an operating system you can balance the CPU performance by adjusting the priorities of the GUI thread and the other worker threads.
In case of a bare metal integration, you can do more processing of your data and less processing of the animations. But due to the lack of an operating system, you have to do the balancing (scheduling). From the GUI perspective, every loop is preparing one animation step. If the time between two loop iterations is delayed, then just the effective frame rate drops.
Ask Embedded Wizard
Welcome to the question and answer site for Embedded Wizard users and UI developers.
Ask your question and receive answers from the Embedded Wizard support team or from other members of the community!