topic Re: App file size and performance in App Development

App file size and performance

jjustingkm — Fri, 25 Jul 2025 17:10:08 GMT

I have an app with file size 10000 MB, does this file size considered to be too much volume? I see performance is not that great. And also would like to know the bigger size would cause an issue to the server performance in addition to the performance of that app.

Re: App file size and performance

james698goff — Mon, 28 Jul 2025 05:12:35 GMT

@jjustingkm wrote:

I have an app with file size 10000 MB, does this file size considered to be too much volume? I see performance is not that great. And also would like to know the bigger size would cause an issue to the server performance in addition to the performance of that app.

Hello @jjustingkm,
Yes, 10,000 MB is extremely large for an app and can definitely impact both app performance and server efficiency. Large apps consume more memory, slow down load times, and strain server resources—especially during data transfers or updates. Consider optimizing assets, compressing media, and trimming unused code to improve speed and reduce server load. A leaner app runs smoother and scales better. mygreatlakes

Best regards,
James Goff

Re: App file size and performance

anat — Sat, 26 Jul 2025 08:10:31 GMT

seems 10000 MB is not the recommended application and you are saying performance also not good.

so try to optimize the dashboard using below tips:

suggest you to review the data-model and to develop like a star-scheme. Further loading only needed fields and records, avoiding any record-id's, splitting timestamps into dates and times and some more measurements.

Further preparing/pre-calculating everything possible within the load script so that simple expressions like: sum(value) or maybe sum({< .... >} value) aren't enough and no aggr() or nested if-loops are necessary.

Re: App file size and performance

Kaushik2020 — Wed, 06 Aug 2025 06:43:06 GMT

There are few tricks which I personally used where the size of the app was 2.5Gb.

Key areas where I did tuning.

✅ Instead of loading load * from table1 / select * from table1 ❌, aggregated functions were used while loading.

✅ Using set expressions (as mentioned above) instead of just sum() or count().

✅ Last but not least, having a Tier 3 architecture where you have separate apps for below tasks.

a. App-1 | ETL, QVD creation if you are doing inside your app.

b. App-2 | Data modelling and loading only what is needed. Key in this case.

c. App-3 | Dashboard - via a Binary load.

feel free to revert in case anything.