Hi,
I would guess it differs greatly for different use cases and circumstances so your probably better off speaking to Matt. But nn my case it was data searches consuming most of my workload. In that scenario, you can find out which elements are running up the usage by going to settings in bubble - click “metrics” on the first page right above where your workload usage/% is shown.
From there filter it to the last 24 hours (or whatever period) and itl show you a pie chart of the breakdown of the usage. In my case most of the pie was data searches. So click on that slice of the pie and it then shows a new pie showing the exact breakdown of the data searches. The colour key on the right of the screen shows the highest % usage at the top then goes down to the least.
From there you can usually click on it again to go straight to that element in your app.
Methods that fixed my problem
Data searches within data searches and repeated searches for the same data/IDs.:
I had many data searches as my app shows a lot of dynamic content on the website. Many were doing searches and also had constraints in those searches that did additional searches (finding an ID for the constraint). Solution to this issue was to simply have a hidden floating group behind the page, this group does a single data search to find my “user/partner/dataset”, then instead of doing additional searches to find the ID I simply refer to that floating group to access the data it’s already retrieved. So now we only do that search once, not every time we need to use the data againn
Switching to option sets where possible:
Bubble doesn’t seem to charge for searching option sets. So things like my reviews and faq’s etc which before searched the database now simply pull from an option set which completely eliminated the workload cost/usage. I can also set attributes against my option sets to filter it if need be.
Search Inputs:
I have a search input which searches a database. we switched this to an option set and replaced the search input with a repeating group/focus group under an input as we think it might be less workload heavy.
Cutting down unnecessary repeated searches by utilising parent groups.:
We had some elements, like buttons etc that showed prices each doing their own data search for the price. We fixed it by simply making the search from the parent group then referring to the returned values of the parent group. (Noob error on my part)
More technical methods to reduce data search workload usage:
There’s a plugin called JSONator alligator or something that can store records in JSON or something then refer to that. We didn’t have time to cover that in the session sadly but it may be our route to completely removing even the most necessary and data heavy data searches.
Again…Matt understands this far better than I do & we simply didn’t have enough time to get into the more technical methods but I would say reach out to him directly he’s incredibly helpful and approachable.
Thanks,
PS, Heres a later test of our workload usage for today. It was 45k per day before we contacted Matt and fixed it. It’s now 1140 per day so super happy with the result.
