Since everybody is on WU pricing now, there are likely lots and lots of small improvements that Bubble needs to make to reduce our WU consumption, which is 100% in Bubble’s favor as the whole WU pricing was presented as a way to reduce loads on servers and impacting performance across all apps and stress on Bubble resources. This change makes developers build more optimally, making the system overall better, so any reduction in WUs (ie: resource intensive operations) is a win win for Bubble and users.
One area that I see as a simple win is to expose more options to database trigger changes. Currently all we have for control of conditions is the thing now and thing before change.
Since we are charged for a database trigger change to execute (not just evaluate, but actually trigger), we should have more control over the conditions to not allow a trigger to execute. One additional value exposed for the conditional should be ‘isn’t live version’ so that we can ensure database trigger changes are not executing in development (we are charged WU for development). Currently all we can do is use an action to terminate workflow using condition ‘isn’t live version’
t
But that still costs…based on below values it would look like we are charged for the evaluation (not changing with new values exposed on conditionals and just is what it is), but also the Inbound call to the data, since the evaluation on trigger will be met and trigger so the data is called, the bytes of data sent (likely for the thing before change and thing now, so a 2X normal cost), the running of a server side action (even though terminate normally on pages would not cost 0.6 WUs in the backend I believe it is classed as a server side action), and the 0.1 WUs for adding to the scheduler (I do not think any backend workflow of any type can get away from this).
So, I would assume if we can have more conditionals to make the database trigger change not execute and only evaluate, we would be able to save about 0.71 WUs.
I’d be really interested to hear other Ideas for features that reduce WUs as everybody should at this point be beginning to uncover them as they develop with WUs on top of mind. Please share them and hopefully Bubble may not procrastinate any longer and start to implement some, maybe in the next Boost Day.