Hey all !
Do you know that a do a search is returning all fieds from the datatype (with privacy rules conditions indeed) ?
But do we really need all this data in our Repeating groups ? No
Do we have to be charged for all this returned data when we don’t need all this data ? No
Do users get apps crashed because of this ? yes
Do we need tons of work hours to refactor database to prevent this ? yes sadly…
So please upvote to this idea : Return only data relevant to a page (page-based privacy rules) | Bubble
Thanks fam!
1 Like
Just to clarify, this doesn’t happen for counts :count (and similar things like average) only returns the count, and not any associated data. All of the counting/averaging is done on Bubble’s server, and then returns only the value to the page.
okay my bad 
and thx
Was confused by the debuguer saying me that I’ve downloaded more than 2megabytes of search when inspecting the do a search. I’m editing my original post so people do not get in error
If you open the network tab developer tools, filter for Fetch/XHR, you can see all the data Bubble sends. Click the request to see what was received. You can easily see which requests are the heavy ones by looking at the payload size
1 Like
As I got you, maybe you can answer this question.
I’ve got a RG with 20 rows. but lot of result in total. On top of this RG, I’ve added a text : RG xyz’ list of users’s count.
Do you think it is best to redo a do a search for this count ?
Back to my “count” load the page 3 times, costs 540 WU to return the total
Imagine paying the bank to find out how much money you keep on there
3 Likes
A count should only return 0.5 WU (0.3 search + 0.2 aggregate query). There must surely be no ‘data volume’ character surcharge as no data touches the client. Again, this is something we can’t calculate that Bubble hasn’t told us about.
Additionally, two identical expressions on the page will only be evaluated once (Bubble will only run one search and send run search to the browser, the results of which can be used by both the places on the page). However, as it stands, that’s charged TWICE for WU despite only ONE request being made. You can see that issue here: PSA: This Repeating Group's X uses WU
Every time Bubble’s informed of a WU issue, the response is ‘we do not have any plans to fix this in the near term’.
This, I believe, will run a new search regardless.
RG’s List of Users: count = RG’s data source:count = Do a search for Users:count
In other words, whenever you reference the RG’s data in another group, you’re essentially just building upon RG’s expression (for WU purposes at least). That’s what I can tell, from my very limited understanding of WU. It’s so stupid.
1 Like
