Today, we’re excited to be rolling out a behind-the-scenes improvement to the way that workflows are run. Workflows with sets of consecutive actions that update the database are going to see performance improvements of around 25% (see below).
Some context: Each Bubble app has a server, maintained by Bubble, which stores its data. When a workflow changes an app’s data, the app sends an update to the server about the new state of the database. This operation can take a significant amount of time, so we would like to minimize the amount of times it is performed.
Previously, Bubble apps made changes to their database one action at a time. For example, if an app had a workflow where the first action is “Make a new thing”, the second is “Make changes to a thing”, and the third is “Delete a thing”, then it would update the database three separate times before proceeding with the next action in the workflow.
Now, Bubble apps are a bit smarter about the way they do this: if a workflow has a set of consecutive actions that require updating the database, the app will batch them all together, send one large update to the database, and continue with the rest of the workflow. Implementing this change led to a noticeable improvement in performance.
Below is a summary of the speed gains that were observed while testing these changes. As the size of the set of consecutive actions increases, so does the size of the speedup.
We hope you notice your workflows flowing a little faster today!