My app is turning out to be exceptionally heavy, with its main table holding 350+ columns, and the user table holding 320+ columns, most of them calculated. I (or someone I’ll hire) need to go through it and make changes to improve performance, as it is barely able to load in the Layout editor and takes too long to load in production.
The app is built full with Glide Tables. I’m wondering if anyone with a good understanding on how Glide processes has a weighted list of things to look for and do to better improve performance? Are there any calculated columns that are significantly more resource-heavy than others? Is performance primarily caused by calculated columns in data (my assumption) vs. the number of components in a page?
Try to avoid building relations and queries using computed columns.
Instead of using a query in a large table that links to a small table…it’s more efficient to build the query in the small table linking to the large table, use a lookup to get an array of RowID’s, and then use a relation in the large table to link to the lookup array in the small table.
That’s a lot of columns, especially if it’s mostly computed columns and that you have so many in the user table.
While the stated limit for projects is 25k rows that’s just a guideline. It’s a technical limit because things slow down, generally at around 25k rows but it’s really about the rows AND columns.
