The data size is big, the App is large, and the App opening time is SLOW. Section Access ensures performance navigating sheets is adequate, but the App opening time of 5 mins isn't ideal. What are the options ?
To provide some background, the source data is approaching 300 million transactions, and the transactions have been entered by approx. 1,000 different entities. Each entity needs to see their own data and no-one else's so an App has been created with Section Access. The App is approximately 10 GB in size. When an entity opens the App in takes approx. 5 mins to open, but after Section Access kicks in and reduces the data down to a single entity, the App performs adequately displaying visualisations in seconds. So the issue is solely the time it takes to open the App. Is there a way to improve the performance of opening the App for each entity ?
Please note :
1. the data model has been extensively tuned and trimmed e.g. it doesn't contain any redundant data or superfluous fields, auto numbers are in use, the model is optimised for Section Access etc.
2. the data model requires unit level data and can NOT be aggregated in the data model
3. smaller Apps have been created for tailored purposes, but a 'wide' and 'deep' App ('the App' discussed here) is required
4. the App takes a number of minutes to LOAD when restricted to a single entity, so on demand App generation isn't a viable option
5. the infrastructure has been optimised within reason
From what I understand, cache warming isn't an option since it doesn't really work with Section Access, since it would need to effectively replicate App openings by the 1,000 different entities, which isn't viable.
At this stage, the only viable option appears to be to split the App into multiple Apps, so entities 0-333 access App A, entities 334-666 access App B, and entities 667-1000 access App C. This is obviously messy and increases maintenance.
Are there any other options ? Please help.
And more generally speaking, how compatible is Qlik Sense and big data ?
