@Eric_Penn beat me to it…but most of that limitation is due to bottlenecks between glide and google sheets. Also if you are loading all 25000 rows on a user’s device, that’s obviously going to slow things down. I’ve tested up to 120,000 rows, but that started to cause severe slowdowns and that was attempting to load all data in one list. Proper use of relations and row owners is going to help with limiting the amount of data that’s transfered. Also switching from Google Sheets to Glide Tables is going to help things a lot.
9 Likes
How do relations specifically help limit the data that’s transferred? I realize row owners is a great way to limit data loading & transfer, but relations? Wouldn’t relations actually add to the amount of data that’s transferred? Or are properly configured relations really used to only pull in data that’s relevant to the user/app in that instance?
In this case it is an app to have control over the sales route. The general manager must have access to the more than 1000 orders per month and they are growing rapidly. This means that in 3 months this user will load the 3000 rows. I think it also depends a lot on the use of the app.
In this case. It would be advisable to eliminate rows of data that are no longer important?
Speaking of this topic. Do you know after how many validations with If Then Else the app could slow down? And is it better to use If Then Else or visibility filters?
Thanks
@Avery_Rawlek I don’t think it limits the amount of data transferred, but it would be less to process on the screen at one time, which may or may not make a difference in speed. Relations are processed on the device after the data is transferred, so it’s not adding to the amount of data that’s transferred. Just thinking that the less that’s on loaded on screen through a relation is less that may have to be processed at any given moment. I’m discovering that there are a lot of nuances that can affect app speed and I’m still learning how everything works in the background. In my app I have one tab that takes a few seconds to open because it’s loading 3000 rows for one user and I believe at that time is when it processes through all the computed columns. All of that happens on the device. The data is probably already there, but it’s all the glide computed columns that I have that can slow things down.
@Francisco_Maldonado It’s really hard to give you a solid answer. Yes, if you don’t need data anymore, you could archive it or just delete it. There’s a lot of factors. Most computed if then columns or visibility settings will have little to no affect on anything. In my case, I have relations on my 3000 rows that relate to those same 3000 rows or to sever other rows of data. It’s a pretty complex sheet, so it doesn’t surprise me that I have some slowness. If your data is pretty straight forward with only a little bit of processing, I think you’ll be just fine. I know there are a few users on this forum that deal with 10’s of thousands of rows and don’t have any major issues.
2 Likes
Oh really great answer. Thanks a lot
1 Like
For my case I anticipate 100Ks row in a year. Within the first week I was already using 40k rows and got discouraged. After some simple GSheet functions like =filter I was able to limit the app to only hold ~5k rows at any given time.
…And those 5k rows are blazing fast because everything beyond that =filter is all built in glide.
6 Likes
There is AppSheet. I tried, but cannot compete with GlideApp. GlideApp is user friendly and you can create apps without much effort.
2 Likes
Geniaaal. I have two questions:
-
How did you manage to have more than 25000 rows if this is the glide limit?
-
Could you explain a bit more about = filter?
Appsheet is good and has a lot of good features. But their prices for applications with login are crazy expensive. Not profitable for small projects or MVP.
2 Likes
This is a good idea. I have one app that’s adding 2.5k rows a week (submissions by 500-600 users/day). Filtering this data to only show today and later would improve the loading time.
Only issue is that it would cause lag in response to the form they fill out and would allow them to submit more than once prior to the sheet formulas resolving.
As I type this, I might have a workaround though…
4 Likes
Super. If you have a solution, could you share it? I have the same problem and I don’t know how to solve it.
Because I’d like my template approved?
First I think we need to understand what constitutes a row.
I.e. You could have 100k rows in a GSheet workbook but only connect one tab of it to Glide lets say for 200 rows. In this case Glide only charges us 200 rows.
Also the 25000 row limit in glide is just a suggestion (I think). If you just connect a tab with 100k rows…sure you are going to have problems. However if you are creative with your data structure you could even pass the Glide row limit without sacrificing performance. This is where row owners comes in. The app grows beyond 25000 rows but no single device downloads more than say 5000 rows.
Regarding =filter it’s a function I use in GSheet to grab only the data from a current date range. You could learn more about it here in the Glide Library
@Robert_Petitto Yes I have the same issue with one form. I tried unnecessarily converting things to math and then using the resulting math as the visibility setting with no success 
2 Likes
Wait patiently, it will happen soon 
Also, I’m working on a website that needs no approval in which you can showcase your apps - it doesn’t even need to be a template!
Bubble.io is really good but doesnt use spreadsheets. it actually houses a database. adalo.com is also great.
1 Like
Why is that statement blurred out, I have to click on it to see it?
'cause it’s a secret for the moment 
El límite de los 25mil filas es por el “trabajo” que significa tener que conectarse a Google y traer todas esas filas y peor aún cuando ni siquiera es necesario, pero puedes tener tranquilamente más de 25mil y Glide no las va a bloquear como las 500 en la versión Free. Una manera de no traerte todas las filas es filtrandolas con Row Owners, pero gracias a las GlideTables todo cambió, ya no hay límite pero de todas maneras la performance va a depender de la lógica de tu app.
Consejo: trata de tener toda tu data en Glide Tables y sólo usa tu GSheet si es estrictamente necesario.
Saludos
1 Like