I see what you mean but your answers have given me a great sense of what to consider here so thanks again.
Each of the users of my app will have 10k+ rows each so Glide’s obviously not the right solution in this instance but at least I know that now.
It might still work. If a user has 10k rows and you are using Row Owners, then that is a small dataset that will be sent from the glide server to each user device. If you have a 100 users with 10k rows each, then you all of sudden 1 million rows of data. That might be pushing it quite a bit for glide unless you look to upgrading to the Enterprise option, which gives you some api and sql access, but you would probably have to make some changes to your app flow. If it’s only a couple of users, then you may be fine. Also, if you switch over to glide tables only, then you can eliminate any possible bottlenecking between glide and the google sheet.
I’m not sure how the data editor would handle such a large number of rows. I have zero issues with my over 8000 rows in one table. Glide has made several performance updates to the data editor since I ran my test with 120k rows.