Hi there, I’m in the process of building a new app that contains a searchable database of a long list of songs (100,000+). The issue is with the current Glide row limits (personal and paid), it would seem that the app would not be feasible for the Glide platform, which is unfortunate since Glide is …

You’ll have to be mindful of your data structure. Row Owners, =filter & =vlookup are your friends. Using spreadsheet formulas could get you there but will be some loss of performance.

Hey Eric, can you expand on this a bit. I’m in a similar pickle as @tourglide but have around 350K rows. :confused:

I had an issue where I needed to do a post code lookup in my app to return the town and German ‘Land’. It’s a 5 digit code (PLZ) … with minimal and unreliable logic… and 12,000 possibilities. The solution is to put that into a separate Google sheet (import csv). Next send a webhook with the PLZ to …

And how does Integromat “report back to your app though?

Making a lookup and paste the values on the row that you are using in order to update the data on the app i think

This should give you an idea of the scenario :slight_smile: @Darren_Murphy is the expert - this is one of his :slight_smile: [Screenshot 2021-06-30 at 23.41.44] [Screenshot 2021-06-30 at 23.42.03] [Screenshot 2021-06-30 at 23.42.33]

Sure, but obviously still with the usual 2-3 min delay?

The webhook is sent immediately to Integromat - so about 2 seconds Then integromat runs every minute (much better than Zapier) The script in integromat takes 6 - 14 seconds to run (with the end point of writing to GS) Then I have my sad wait time for the Google sheet: if I am updating a row, th…

Just use glide action to set columns in google sheets with a values to filter, and have gs do the filtering… and glide to show that sheet data, it will take 1 to 5 seconds to complete

It depends on the size of the data set. An array formula with a lookup in GS runs every time… every row. This could get painfully slow very quickly, and is unnecessary because ideally the value is fixed once you get it. A lot depends on the use case and the specifics of the App.

Workaround for searchable database containing 100,000+ rows?

Ask for Help

Lucas_Pires June 30, 2021, 10:49pm 15

Btw @Messias_Carvalho already done a video about it Take a look

Delete rows and make more rows

Topic		Replies	Views
App doesn't work with 65k rows of data Ask for Help	6	767	October 18, 2021
Any suggestions to have more rows beyond 25000? Ask for Help	11	1888	March 8, 2022
How many rows of data can Glideapps handle comfortably? Ask for Help	2	649	December 12, 2021
Delete rows and make more rows Ask for Help	16	1167	July 20, 2021
Are there any other sites like Glideapp? Ask for Help	49	1776	February 5, 2021

Workaround for searchable database containing 100,000+ rows?

Related topics