Heyy!
I have a really big data type on my bubble app, basically actors forms. And my admin panel where i see all this actors is consuming 20k WU a day. Im reading all this data on my RG with a “:make static” because i dont want my RG being updated every time a new actor joins, but i think thats causing all that WU consuming because of having to read every single field of that data type to make it static.
Is this right or no? PLEASE HELP jajaja
@produccion1 , you don’t want to use :make static (this will actually load more data) - you can view this in your network tab.
What are you trying to display?
Basic info first like names, age..etc and if you click on top then shows the complete data about the actor (video links, size, hair color…etc)
¿How should i config this to have the best WU performance?
I would recommend making the repeating group static, with 10 or 15 entries, and using pagination. Another option is to not display anything in the repeating group, and instead include a search field so that when the user searches, the results are filtered to show only the actors they’ve searched for.
No, that doesn’t seem right.
I have apps with many more records than that and they don’t generate that kind of consumption. Most likely, your data type has too many fields. So here’s something to think about: how many of those fields actually need to be displayed in your RG?
My suggestion is to create a satellite data type containing only the fields you actually need to use in the RG, meaning only the fields that really need to be displayed. Then, create a relationship between this satellite data type and the original data type. When the user clicks and opens the page, then you can use the original data type.
To populate and reference this satellite data type, you can use database triggers in the backend. That should be pretty straightforward to set up and make work.
@produccion1 , generally this kind of usage is OK. Bubble does what’s called lazy loading (bubble will load a little more than the screen size), so even with 50K records the searches won’t consume too much WU. There might be a setup with your search where this isn’t working properly, these include:
Good suggestion @hugojmenezes , but you’ll only need a satellite data type if the data has lots of content (think 1000 words + in a field)
You could explore pagination as @pbenito has suggested, but you also shouldn’t need to make this static, unless this data is being changed constantly - the best approach would be setting the values in a state (as these don’t automatically update)
