@florent.bocquelet, re:
So what you are saying is that it is actually more efficient to have a “Company” field in each invoice and then do a “search for…” on the invoices with a constrain on the company, rather than having a “Invoices” field in “Company” that is a list of invocies, and directly display this list without passing by a search ?
Intuitively, I would have think the opposite (using a list you don’t have to perform a search on all invoices, you already know them)
You’re not wrong. To be more precise, using a list is faster, but having the company field is more scalable. If your list is short – you know you’ll never have more than 20 - 30 invoices per company, for instance – then yes, using a list will load a little faster. However, using a company field isn’t that much slower, and it’ll still be fast no matter how many invoices per company you have, whereas the list will start slowing things down once the total number of invoices goes beyond the number you actually want to display at any one time.
@ryanck
About that quote, I cannot use the infinite scroll mode because below the table I´ve the totals and it looks really really weird. And sorry to say that but I´ve used other tools like Knack and Caspio1 and they don´t have any issue even when showing 300 items and more at the page load. They could take about 10 seconds max. But nothing compared to those 3-5 minutes of Bubble.
Yeah, 3 - 5 minutes for 300 items is slow for Bubble, too . There’s probably more going on than the sheer number of items in that case.
Anyway, the total time is equal to 300 multiplied by the time it takes to load each one. So if the time it’s taking to load each one is high, things can get slow very quickly. Generally it’s easier to squeeze down the total amount, but if you want to display 300, (although chrisloarge305’s suggestion is worth considering), you need to make sure each one loads very quickly. On that front:
-The number of total elements in each cell of the repeating group controls how much javascript time it takes to render them. If your browser freezes while the page is loading (ie, scrolling up and down don’t work), you’re probably hitting a total number of elements issue, and the thing to do would be to reduce the elements in each cell.
-If your browser is not freezing (you can freely scroll up and down while it loads, animated loading indicators continue to be animated, etc), check to see if each cell uses any data beyond the invoice itself. If each cell contains a search that’s based on data from the invoice, you’re doing 300 searches all at once! Or if you’re getting sub-objects of the invoice, like the invoices’ line item’s … etc., that’s also loading additional data for each cell.