Optimizing search WUs: Daisy chain filtering vs conditional data sources

Tips
1

Since launching a few days ago I’ve burned through over 250k WUs and it seems that nearly 50% were consumed because of a single search/RG that includes multiple filters and sorting activities. In researching, I came across the “daisy chain” method which uses cascading workflows and the :filter operate to stack filters, instead of depending on conditionals that change data source to a new “do search for” event. It’s been a few hours and I haven’t seen much change in WU consumption, if at all.

Looking for anyone that has experience with this sort of UI — stacking filters and sorting for a repeating group. I can’t believe the amount of WUs I’m consuming for what seems like such a common user experience. Is this normal? I don’t really understand how anyone is meant to start a business on bubble, much less scale one.

Screenshot 2024-07-07 at 5.01.41 PM
Screenshot 2024-07-07 at 5.01.41 PM2540×730 31.7 KB

Screenshot 2024-07-07 at 5.01.34 PM
Screenshot 2024-07-07 at 5.01.34 PM2538×918 193 KB

2

Use a different backend homie, then the front end.

I won’t say where. But they rhyme with… he-web and poopabase

3 Likes
3
  1. Is the data type you’re searching for heavy (lots of data stored on it)?
  2. Have you verified you don’t have any nested searches in your search expression?
  3. Have you ensured the search only runs when it really needs to (i.e when the RG is visible on the page), by making the data source empty by default, and only conditionally setting the data source?
  4. Can you optimise the sorting so you only do one sort in the entire process?
2 Likes
4

Tip 1 : Condition 1 is yes and do a search for count is not 0 data source : do a search for pens , when you do this Bubble should run condition 1 and don’t run count if condition 1 is no , however it doesn’t do that , so you need a seperate group that holds count’s value , such as this > group type number when condition 1 is yes , data source : do a search for count

Tip2 : When you have a dropdown that has values fetched from db don’t directly put it on choices source , it will call all of them regardless. Do this, > lets say your dropdown choices are text , 1) create option set that have 2 items , make dropdown choices source these options ( to not get error ) , and in conditional when condition 1 is yes , choices source do a search for your actual options .