I’m having substantial troubles with page loading an RG. With upwards of 50 rows it could take several second to load, often greater than 10 seconds. It appears to be related to the number of rows, not the number of elements in the row. I could have a dozen elements or 3, it seems to be the same. Is this typical? Is there a better way to handle the load time? I would not have thought 50 was a substantial number of rows to cause delays.
5 elements does not seem like a lot. The number of rows displayed is controlled by an input.
I also have substantial ongoing “PAGE UNRESPONSIVE” problems, that could be related. This has been going on for months and bubble support has not been able to help. All they can say is clear the cache, which I now do regularly but does not help.
Pagination is simply showing a set number of rows, say 10, and then having click “next” or “back” to cycle through results. there’s plenty of tutorials on that here and on YouTube.
I had not previously had this slowness problem with all the RG and charts I use. I haven’t worked with other pages enough to see if it’s the same. One change, the chart plugin was updated several weeks ago.
Please provide screenshot of the source of “list of numbers”. I got a couple theories.
Pagination won’t really matter as he’s using a plugin that force loads all the data anyway then refers to it using the RG.
He’s either got a massive dataset that the “list of numbers” element is referring to, referring to data that’s then filtered/advanced filtered, or referring to a thing with a lot of nested “lists of things” in his data types.
the issue seems to be happening client side so it’s most likely the filter/adv filter or a massive number of rows being force pulled all at once via that element or a combination of the above issues.
Possible other data issues on the page like popups referencing too much data or too large of nested lists and bad data structure since he said it’s not just on this page it’s on all pages.
There are 3 inputs that are data for the graph. Each input comes from a Financial Calculator plugin. The ListofNumbers as well as this just doesn’t seem that heavy in data use. In fact, it’s ONLY the page load function. When variable user inputs change the response on the chart are instant (with a few exceptions but that’s another problem).
Instead of displaying all 50 rows at once, consider limiting the visible rows and implementing pagination or infinite scrolling. This will load fewer items initially, reducing load time.
Thank you Kipy for taking a look. I’m using all the 50-row data in a graph so all the data must be available.
Due to the “unresponsive page” errors using different devices, I’m beginning to suspect I’ve reached the limit of browser ability (on any device) and that’s what’s hanging up the RG. My editor might be getting too big for the browser to easily manage. Is there a limit where the number of pages or user fields in my app gets too large for the browser to handle the editor well?
Maybe you should use a simple JavaScript code snippet to calculate all the financial data on page load, and then feed your RG and chart with this data. On many occasions, I’ve found that using JavaScript is much faster, more efficient, and more elegant compared to using multiple plugins that require maintenance and are often buggy.
I see that you are using Toolbox, so you can easily implement JavaScript code using an ‘Expression’ element or the ‘Run JavaScript’ workflow action. Additionally, such code will run once, calculating all the required data, compared to 150 runs (3 fields × 50 rows) that you currently have inside the repeating group. This should significantly speed up page load, I guess.
I also think that AI will easily generate such JavaScript code for you
