We have a glide app that currently uses native Glide tables (both regular tables and big tables). We also have a backend in AWS to do certain things that we cannot do in Glide. For it, it reads our Glide tables and updates them by using the Glide API.
My question here is, if my table has 1000 rows, does reading it count as 1000 updates?
I ask this since we’re seeing a huge increase in the use of updates (around 5k daily) and think it might be related to the reading of the tables.
Also, if instead of native Glide apps we just connect to postgres and use the tables that exist in our AWS backend, all operations also count as updates in them?
When you are reading rows via the API, each API call counts as one update.
When adding/editing/deleting rows via the API, each mutation counts as one update. So if you update 1000 rows, that’s 1000 updates.
I believe that reading the tables would not consume any updates, but updating them would.
1 Like
Thanks for your answer. If it’s not a bother, I have another question since we’ve contacted Glide support yet we cannot seem to understand where the increase in our updates is coming from.
When we go to the usage page, we have five things:
- Glide Query API
- Glide API
- Trigger Webhooks
- Call API
- Glide AI
Glide Query API is the one that is consuming the most updates. We asked support what does this mean and in what’s the difference with Glide API (since we hadn’t encountered this term before and it’s not on the docs), but all they said is “Glide API does Add, Edit, Delete; Query API can get rows. Each Query consume 1 update per 10K rows”
Are query columns inside Glide considered a Glide Query API? if I have a table with 3000 rows (which is the biggest table we have) and through another table I make a query column with it, display it on my front with a search bar and make multiple searches through it, does that count for an update as well?
I don’t believe that’s the case. The query column in Glide and the Query API you’re using are different terms. If your dashboard shows usage from Glide Query API, I think it’s referring to your “reading” queries, which consumes 1 update per 10K rows.
Whilst it’s strictly true, “1 update per 10k rows” is misleading in my view.
When reading that you could easily be forgiven for thinking you could make 10k API calls, and if each call only returned 1 row then that would be a total of 1 update. But that’s definitely not the case.
A better way to put it is “One update per call, and each call will return a maximum of 10k rows”.
And yes, the Query API has nothing to do with the Query column.
That surprises me. I’d suggest having a close look at how you are using that. As I said, you should be charged one update for every query API call that is made. Assuming that you have logs, it should be easy to cross check this.
1 Like