Search or Filter ? (performance)

Questions
1

Hi Bubble Community :blush:

I’ve gotten into the habit of creating “list” fields in my tables.
For example, all events corresponding to a project are found in an ‘event’ (list) field of the ‘project’ table. So I don’t need to do a ‘search’ like ‘Search for event > project = this project’ (which would search in all my users’ projects), but rather I use “Parent project’events.”

Can you confirm that this uses less WU and is more efficient?

But when I need to filter this list, I wonder. Is it more efficient and less WU-consuming if I do a ‘search’ or if I filter on a list that’s already been ‘searched’ and is available on a table ?

I hope my question is understandable. :sweat_smile:

Thank you !

2

If you process data that is already loaded to the client, then there are no WU costs. WU only applies to any backend processing.

Performance degrades when processing very large lists client side.

As a rule of thumb for me, i prioritise User Experience when making deciding on whether or not i should expend WU.

3

Perhaps this is another way to think about this.

Since the events are already on the page:

  • Basic fields = free filtering
  • Cross-table or computed logic* = WU filtering

* Advanced Filtering