When u write a condition on an action - to let cases that doesn’t meet the condition avoid the action - does this improve performance, or i’m gaining nothing, since bubble has to read through the condition, which also uses time?
It depends on how you look at it. If a simple condition stops Bubble from performing an unnecessary complex action, then you have increased performance, yes. If the condition itself is complex, then it may slow Bubble down more than the action, in which case you might as well run the action regardless (from a performance perspective).
There really is no difference between an action and a condition, performance-wise. They both depend on the same queries to the same database, so a good rule of thumb is to keep your conditions just as efficient as your workflows, and remove the unnecessary ones.
1 Like
As @petter said, If you have an action modifying 40 fields in the database, and the condition isn’t valid, then yes, performance is improved (save a lot of seconds).
1 Like
This topic was automatically closed after 70 days. New replies are no longer allowed.