Forum Documentation Showcase Pricing Learn more

Improving Repeating Group Loading Performance


#1

The very slow loading of a repeating group with over 100 records has been discussed before. Improvements on repeating group performance

Apparently, this is a known limitation.

However, I found it interesting that the warning icon in the bottom right of the Workflow Debugger did not suggest buying more capacity.

Is this because more capacity will not help load the repeating group faster, or is the loading speed of the repeating group not being measured?

@ryanck
@romanmg
@emmanuel


#2

What expression did you use for the repeating group’s data source? Database structure has a massive effect on search speeds. Also, what display type (full list, ext. vertical scroll, etc.) did you set for the repeating group? These things have an impact on a repeating group’s loading speed just as much as the number of items being displayed.

Daniel


#3

Search for, merged with another search for.

full list, which is needed


#4

this doesn´t solve your problem from a loading speed perspective, but if you show a loading screen while the RG is loading, you can improve the user experience


#5

I would surmise the issue is not necessarily the repeating group but more the fact that you’re doing a search merged with a 2nd search and then attempting to display “full list”… Try applying the same rationale and simply displaying the text field and see how quickly you get the results back… In many cases when things are slow we need to rethink from the ground floor up how we structure stuff in order to accommodate the requirement… And sure this very good reason you’re attempting to display full list but as I’m sure you know this is not ideal. Pagination is always a good option if your user case allows


#6

dbevan You mention a few considerations. What is the best choice for each? We have 125k records with 8 fields per record, so we want to minimize page load time, the load on the server, etc. Thanks!


#7

The less data you have to display on page load, the better. There should be no need to display 125k things at once so figure out ways to deliver only what users need to see.