Hi, I have a few questions regarding data management and performance in Glide apps:
User-Specific Columns:
If I use tables with only user-specific columns to store data (e.g., for a step-by-step process), where are these data stored? Do they have any impact on app performance for the user? Additionally, is there a limit to the amount of data that can be stored for each user under the Maker plan?
Tables with Non-Specific Columns:
If instead of user-specific columns, I use tables with many computed columns (e.g., relations, lookups, or formulas), will this have a noticeable impact on app performance, especially with a high number of users?
Large Users Table:
If my "Users" table grows to over 20,000 rows, could this affect the app’s performance or data loading speed for individual users? Are there any best practices to manage large user bases efficiently in Glide?
User specific data is stored in the Glide back end (server-side).
No.
The only limit is the row limit, which is 25,000 rows per App (or 50,000 with Big Tables).
Yes, no, maybe. There is no one size fits all answer to this. It just depends. It’s possible to have 500 computed columns in a table with zero impact on performance. It’s also possible to make an App completely unusable with just a couple of computed columns. It just depends how they are being used. That said, there should not be an either/or choice between User Specific and computed columns. That’s like saying you want to choose between a banana and a bicycle
If you have a large users table, you should definitely use Row Owners.
