Thanks for your reply!
I actually initially had all the repeating groups sourcing from the database, however I was encouraged to restructure based on the hidden repeating group from this post; Any ideas on speeding up read/write to database? in order to help speed the page up.
In terms of performance, its not too bad right now - much better then previously. If you have any ideas on how I could structure it better I’m all for it!
Unfortunately, given the complexity of some of the searches I have to use the filter modifier (which was pointed out to me in another post). The hidden group currently searches for all of the stuff each repeating group has in common - and then each of the 24 (yes, 24 repeating groups!) filters based on that information.
Here is a link to the public app I just created - [removed - please ask for the link] - including the data (though I may remove it given some of its sensitive nature - this app is currently live in our organization).
EDIT: Also, if you struggle loading up the editor - add &issues_off=true to the end of the URL. The crazy amount of stuff going on in the page means that the issue checker goes nuts and will lead to huge performance issues (in my experience anyway).