App loads are slow in Qlik Sense Enterprise on Windows Hub: What to consider

[Andrea_Bertazzo]

A Qlik Sense App may load slowly in the Qlik Sense Enterprise on Windows hub.

Resolution

Qlik advises following our best practice guides when designing and publishing an app.

See:

• Optimizing app performance 
• Best practices for data modeling 
• Best practices for choosing visualization types 
• Best practices for designing visualizations 

In addition, the following five points may impact load times:

Qlik does not recommend against using the options below, but to keep them in mind when designing an app or measuring its performance. For a more hands-on and individual appraisal of your app and how to streamline it, please contact our professional services.

1. Session access
   
   Session access evaluation has not cache, it is always evaluated on each app open. So it is important that the section access script is optimized to avoid loss of time at any opening.
   Group based reduction is a great improvement recommended to shorten Session Access list and make calculation cache reuse more efficient.
   
   Defining data reduction by user ID adds unnecessary processing and calculation cache segregation. Changing to group-based reduction adds a noticeable performance improvement.
   
   
2. Security Rules
   
   Wide use of string-based "like" comparison instead of "=" comparison in rule leads to large processing overhead. Try to use fewer and simpler rules to speed up the opening process.
   
   
3. Static Content should be reduced whenever it is possible
   
   In particular, thumbnails images for the sheets in the app overview, leads to a noticeable time cost for the download. Part of processing time is derived from security rule evaluation per image, which improves with the security framework.
   
   If possible, avoid to use unique thumbnail images for sheets and choose one common logo image for all.
   
   
4. Calculated dimensions
   
   Reduce the number of calculated dimensions or dimensions defined by an expression. For more information, please, follow this article.
   
   
5. Network
   
   Network aspects should also be taken in consideration, especially if the delay occurs more often when users connect from home than from the office, or from a region more that others.

[Deepakdk]

1) A person having large set of data will have application more than 4 GB. If qlik recommends the application size to be less than 2 GB then its not a tool for large enterprise.

2) If section at basic row level cannot be applied then there is no governace on the dashbaord leading to security threat.

3) If sheet doesnt have images which are different then its diffcult to understandbetween reports when you have larget amount of sheets.

Overall the artick suggest that the qlik cannot be used for larget and complex set of data.