Skip to main content
Announcements
Live today at 11 AM ET. Get your questions about Qlik Connect answered, or just listen in. SIGN UP NOW

Delay on opening App when section access is used

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Delay on opening App when section access is used

Last Update:

Nov 3, 2020 8:12:37 AM

Updated By:

Andre_Sostizzo

Created date:

Oct 31, 2019 7:24:59 AM

The same document/app takes more time to open (up to 3-5 times more) when Section Access (SA) is applied.
This occurs especially if the file is large and if SA performs many selections (reductions) on it.

Environment

  • QlikView, all versions
  • Qlik Sense Enterprise, all versions

Cause:

Section access will always need some additional overhead to evaluate the authorization and to perform a data-reduction.

When a user opens an app/document with SA, a table is created in-memory with all of the reduction fields applied. The data is then reduced, hypercubes are re-calculated as needed, and then the application is displayed to the user. The higher the SA table complexity, the longer this process may potentially take as the reductions needed increase in complexity. These reductions add to the cache, which may not get flushed if not needed by the OS due to working set reaching upper limit.

Resolution:

It is possible to mitigate the problem optimizing the document /app:

  • Optimize the Data model and especially the objects in the GUI.
    • Remove objects from the landing sheet (for QlikView).
    • Move complex expressions to the script whenever it is possible.
    • Avoid tables with large quantity of data.
  • QlikView Only:
    • Disable data-compression under Settings > Document properties > General. This option helps to save some storage space in the disk, but it costs time and resources by decompressing.
Contributors
Version history
Last update:
‎2020-11-03 08:12 AM
Updated by: