I have been building with Glide for about a year, but mainly exploring the app and creating personal projects.
I have garnered the attention of some friends who have businesses that want to implement digital solutions and I know I can build them with Glide!
The problem is, these are more heavy in computed columns and have way more rows.
So, even tho I have built and dedicated a lot of time to build nice solutions for their problems, I am worried about one thing:
If I have an app, that:
- Has, let’s say, 23000 rows
- They are split in pages that each, by using row owners, just has about 10-30 rows that a user downloads
- Each page has at most 5 relations with lots of look-ups and some math (in one page in specific, the worse, it has about 30 lookups)
Does using row owners “guarantee” my safety that the app wont be slow and it can scale to those 23000 rows, or should I be warry of it “collpasing” in loading times long before that?
The app can slow down when users table is large and that you have multiple rows with row owners. But it shouldn’t be unusable.
I would suggest you to use big tables since you are very close to 25k max limit of glide table.
First of all thanks for the quick reply!
Glide tables are not an option for now due to some computed columns limitations.
To clarify, I am not near the 25k but I am just wondering what would be the limits before asking for a price to build it
Just a general question, don’t row owners make the app faster since people don’t download all the information?
So, irrespective of how many users (of course if there were thousands it would be different) If each had a row owner shouldn’t it not have an impact on the app?
Got ya.
It is actually the opposite. It is slower because the server has to filter data before sending it to the client. That may not be a problem with 100 or 1000 users and row owners. But you would probably start to feel it a bit while increasing the number of rows in the users table. Tho, it is gentle, don’t be afraid 
. It is not a huuuge slowdown. It really depends on the number of rows, number or users, roles and row owners column.
You should be ok!
Ahahaha I really am stressing a lot
I am not thinking of having more than 200-250 users
But I am worried to say I can have them and then it slows down to a point where it is not the best User Experience.
Well, I guess I have to deliver it and learn next.
thank you very very much
250 users! You won’t see any slowdown because of row owners! Be reassured!
1 Like