Most computed columns in Glide actually compute directly on the user’s device, so the response time is instant as there is no waiting for data to sync. If computations happen on an external database, then any changes to data need to first sync to Glide servers, then sync to that external data database, then wait for that external database to do any computations and sync back to Glide whenever it feels convenient, then sync back to the end user device. So it comes down to doing the computations directly on the user’s device…or waiting for data to sync across multiple servers, compute, and sync across servers back to the user. One way is clearly the winner. It’s the same case regardless of external database used. Some are better than others, but there is going to be a noticable delay if your computation logic is not within Glide.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Speed optimization of the app | 10 | 499 | January 19, 2022 | |
| How to improvize speed | 4 | 595 | August 31, 2021 | |
| Add spreadsheet computed column | 4 | 612 | July 23, 2022 | |
| Result of calculations on a different page | 1 | 103 | March 6, 2024 | |
| Bulk data update | 7 | 243 | November 11, 2022 |