Suggestions Required for Reducing App Size on Qlik Cloud
Hi All,
We are currently facing challenges with the increasing size of one of our Qlik Cloud applications. Below are the key details and constraints:
Initial App Design: The app was originally designed with data aggregated at the monthly level, resulting in an app size of approximately 1.5 GB.
Requirement Change: A few months later, a requirement emerged to analyze data at the daily level. After this change, the app size increased to ~3 GB.
Recent Change – Ageing Buckets: In a recent enhancement, we introduced ageing buckets in a large transactional table.
Prior to bucketing: ~5 crore (50 million) rows
After bucketing: ~13 crore (130 million) rows
Current app size: ~7 GB
Data Volume: We are only loading 3 years of data in the app.
Insight Advisor Constraint: The app also has Insight Advisor configured. We are considering splitting the app into two using document chaining to manage size, but we foresee a major limitation:
If a user queries from the landing sheet using Insight Advisor, it may not support document chaining to the second app, which is a blocker from a user experience standpoint.
Kindly suggest a feasible approach or workaround to help reduce the app size while considering the above constraints. Specific input on how to retain Insight Advisor functionality in a document-chained environment would be particularly helpful.
Great dreamer's dreams never fulfilled, they are always transcended. Please appreciate our Qlik community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
It's not quite clear what's meant with the aging buckets but it seems to duplicate the data in some way. Maybe this could be prevented with a special kind of dimensional table to address overlapping areas, like:
