Hi there! I am creating an App in a Premium ...

(Aparicio Piñeyrúa) #1

Hi there!

I am creating an App in a Premium plan.

This App needs to have about 37 tables for Ref values only (the bigest one of these tables is going to have 2 columns per 1100 rows and the average tables are 2 columns per 40 rows), plus other 20 tables where the users are going to add new rows every day (average of 10 rows per 30 columns per day).

I can´t seperate this tables into several App´s.

How do you think it is going to be the behavior of the App?

(Mary Jane Pender) #2

Hi Aparicio,

What specifically are you worried about?

Is it running out of database space or the number of ref columns?

Because, based on the limited information you have given us, I don’t think either of those cases is a problem.

Let me know what your concern is.

(Mary Jane Pender) #3

If you are worried about hitting the maximum data in the google spreadsheet, you may want to split the tables up onto 2 Google spreadsheets (each with many tabs for your tables).


you are worried about performance, you may want to look at loading a view of a slice of the data based on something like UserEmail() or some other category.

(Aparicio Piñeyrúa) #4


I´m worried about performance.

(Mary Jane Pender) #5

For each table in google, you can help performance by deleting any empty columns to the right of the last column in the sheet.

You can do the same with the rows.

Delete any empty rows after the last row in each sheet (Appsheet will insert any rows if it needs to).

You can also use a delayed sync so that the user can add a number of rows of data before choosing to synce – reduces the wait.

Here is a snippet from the Support documentation:

How to improve read-only Sync performance Conceptually, there are six ways to improve Sync performance:

Choose an efficient data provider Reduce the amount of data transferred during Sync Reduce the amount of computation (for spreadsheet formulas and virtual columns) performed during Sync Fetch or compute data in parallel (relevant if there are many tables in the app or many expensive virtual columns) Use a fast network (this is relevant for the connection between the device and the AppSheet Server) Make Sync happen in the background so that the user does not need to wait for them to complete. These are explained in greater detail in this article. As an app creator, you have many options to control these aspects of Sync performance.

How to improve Sync performance when there are data updates Data captured or updated by the app on a device needs to be sent to the cloud provider backend. This can be one of the slowest aspects of the Sync process because the changes have to be made sequentially (to ensure correctness). Conceptually, there are four ways to improve this aspect of Sync performance:

Reduce the number of updates Reduce the amount of data sent with each update (eg: images captured per row) Reduce the amount of computation (eg: workflow rules) that must happen with each update Apply these changes in the background so that the user does not need to wait for them to complete.

Hope this helps.


(Aparicio Piñeyrúa) #6



(Mary Jane Pender) #7

hope it helps.