@Kirk_Masden โ very good guidance from you to treat โrendering performanceโ or โinteractive performanceโ in a different category from sync performance.
Rendering performance is really about what we ask the device/browser to do when a users taps on something or scrolls something. The processor on a device is slow and if you ask it to do a lot of computation, it will make the UI feel โsluggishโ (takes a noticeable time for a UI response). Expensive format rules fall in this category, as do expensive searches, as you point out. Also, if you had a very large data set and open a view on it, it could be slow if all the data has to be processed in some way (still, the example you had of a view with 8000 records feels odd to me).
If a format rule is disabled, then it is not computed and therefore there is no impact on interactive performance. Now if your app had a thousand disabled format rules (for no good reason) then it will probably need more memory resources, the system would loop through the thousand rules, check each of them and decide they are not to be applied, etc. So some overhead for a pathological case like that but not in the normal cases.
LinkedIn
Twitter
