I have a Data Type with 1000 items which I am displaying in a Repeating Group on a “View” page right now. This “View” page is only for Admin and the end user is not concerned with it. I can keep filters which will limit the number of items being displayed to maximum 100 at a time. However, I am not sure about all the pros and cons of both these scenarios. I know that with filter I would be retrieving less amount of data and getting a much faster response. Are there any other benefits in addition to this? As in less workload units consumed or something like that.
This is what our Bubble AI suggested:
Great question! You’re absolutely right about faster response times with filtering, and there are indeed several additional benefits:
Workload Unit (WU) Consumption Yes, limiting your data retrieval does reduce WU consumption! When you fetch fewer items, you’re using less capacity since “the amount of data being sent can vary dramatically” and affects performance. Our system sends all data saved on a thing when queried, not just what’s displayed, so limiting to 100 items significantly reduces data transfer.
Performance Benefits Beyond Speed
-
Reduced element rendering: A repeating group with 1000 items creates thousands of front-end elements (1000 rows × your elements per row), which can make pages “visibly slow to load and choppy to move around.”
-
Better database efficiency: Keeping filtering “as close to the original search as possible” means our system can optimize queries at the database level rather than processing all 1000 items first.
Filtering Approach Matters Use database-level constraints (in the search palette) rather than the :filtered operator when possible. Advanced filters can “drastically decrease efficiency” and increase WU consumption by potentially performing multiple searches.
For your admin view, limiting to 100 items with proper database constraints will give you faster loading, lower WU usage, and better overall performance.
Thanks for your reply.
This topic was automatically closed after 70 days. New replies are no longer allowed.