topic Re: reduce size of app in App Development

reduce size of app

Manni_SM — Tue, 26 Aug 2025 16:11:06 GMT

Hi @rubenmarin @marcus_sommer @robert_mika

i have Qlikview applications with the sizes of 160000MB (16GB) 8GB,5GB with three layer architechture

now custmer is asking to migrate apps Qlikview from Qliksense . as those applications not able to open in Qlikview its hanging due to heavy size

there is no much logics involved . only issue is they have 10years data into app.

now customer dont want to delete the data and asking to reduce the app to 500MB or 1000 MB below

which approach is best to follow ? any ideas? any suggestions will help ?

Re: reduce size of app

robert_mika — Tue, 26 Aug 2025 16:57:00 GMT

@Manni_SM I would say it depends on your architecture, but if you are not able to open with data, try to open without?

You still have access to scripts and front end so you can rebuild that in QS.

The I suggest to aggregate the data and load only the part you need.

Re: reduce size of app

Manni_SM — Tue, 26 Aug 2025 17:15:19 GMT

Thank you...

But in UI there is only one table with 4-5 columns no major calculations.

But customer need all 10 years data so script also no much calculations

So how to reduce the size ?

Re: reduce size of app

QFabian — Tue, 26 Aug 2025 19:33:49 GMT

Hi @Manni_SM , some basic ideas :

commenting unused fields

cutting decimals in numbers 1,090223212 --> 1

reduce lenght of text of "comments" fields

take off time in date time fields

make some aggregation, maybe now the data is available daily, then you can try grouping weekly.

greetings!

Re: reduce size of app

rwunderlich — Tue, 26 Aug 2025 22:43:43 GMT

This blog post presents some strategies for reducing data model memory,.

https://qlikviewcookbook.com/2024/11/reducing-qlik-field-memory/

The post is written using Qlik Sense and QSDA Pro but the same principles apply to QlikView. You can use the QV Document Analyzer to get field sizes if you want to start the trimming exercise in QV.

https://qlikviewcookbook.com/recipes/download-info/document-analyzer/

If you want to do the tuning in Qlik Sense, remember that you can load a subset of the rows and still do valid tuning to reduce the overall size.

-Rob
http://www.easyqlik.com
http://masterssummit.com
http://qlikviewcookbook.com

Re: reduce size of app

Manni_SM — Wed, 27 Aug 2025 05:42:30 GMT

Thnks @rwunderlich @QFabian @ for your suggestions

But the data we have to show as it is. 10 yrs data in UI customer want in stright table

Shall I use ODAG if yes how to use any guidance? How to start am new to ODAG

Customer suggested ODAG

I need some steps like I have

Qvd loader layer

Transformation layer

Ui - presentation layer

How to perform ODAG on these three layers

Re: reduce size of app

marcus_sommer — Wed, 27 Aug 2025 06:13:56 GMT

It's quite simple - if the data-set + data-model are already well optimized the data-size couldn't be significantly reduced and it's only a question of purchasing enough resources.

That's a rather rare scenario even if experienced people designed the environment because the most development projects starts more or less iterative with a focus on development-speed and functionality. Performance is secondary as far as the run- and response-times are acceptable. If it worked it won't be further improved.

Therefore I suggest to take another more careful look to the already provided hints because the aim is not to change the information else the way how the data are stored and associated and there is often a significant potential of improvement. A very classic case would be the split of a timestamp into a date and a time field - the information would be further there but the storage/RAM consumption would be much smaller.

Beside the above you shouldn't not to disregard changes to the information too easily. For example it's quite common to analyse the data of the last n periods to an atomic level, for the periods before to maybe two years it may enough to look on a daily-level and for the elder periods it may a monthly-level. Such approach could be included within a single fact-table and will decrease the sizing significantly without a loss from an analytical point of view.

Fact Table with Mixed Granularity - Qlik Community - 1468238