Internally the scheduler updates each animation frame and updates the progress (percent data binding). There is a noprogres attribute that you can add to prevent it updating on progress and that would prevent the many executions. I checked in Wappler and it seems that the option is missing on the UI, we will see that we add it to the UI.
When you have large pages with lot of expressions and formatters which also updates a lot then you will certainly notice that in performance. Trying to keep data changes and the number of expressions to a minimum will be good practice. The evaluation of the expressions are fast and cached, but having too many can cause performance issues. An other optimization that can be used on large pages is the usage of conditional regions, the conditional regions removes its content from the dom when the condition is false and that also prevents the expressions within from being evaluated. Hidden content like with dmx-hide will still update in the dom and all expressions within will be evaluated while it is not visible to the user, but will impact performance.
