Skip to main content

Reporting Service

This forum is for discussions around reporting from Qlik Cloud.

Announcements
Action-Packed Learning Awaits! QlikWorld 2023. April 17 - 20 in Las Vegas: REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
TusharDev_Qlik
Creator
Creator

QlikSense App access performance issue

We have an app which is 10 GB of size. Recently we started facing severe performance issue like extreme slowness and timeout issues for end users. I wanted to know if below things affect the performance.

1] App reload is scheduled daily so having simultaneous app reload and app hub access is creating an issue?

2] Considering the size of the application how can we accurately measure its CPU and RAM footprint per user?

3] App cache time is currently 8 hours which is default, do you recommend reducing it to lesser time as RAM will always be occupied if the app is constantly in use.

 

 

Labels (1)
2 Solutions

Accepted Solutions
Frank_S
Support
Support

I suggest that you start with evaluating performance of your App using the following.

You can use the performance evaluation tool to discover detailed information about the performance of your apps and components therein. Once you have done a baseline evaluation, you can then start to compare evaluations for changes in performance against future evaluations.

 

Once you see the differences in the evaluations, you can see where the performance improved or declined based on changes made.

 

If you don't have an existing baseline to work from, you will still see performance results of individual app components.

 

From this, you can then apply the suggestions found here based on the evaluation findings.

Kind regards...

 

Please remember hit the 'Like' button and make helpful answers as 'Solution Accepted'... Cheers!

View solution in original post

rwunderlich

I suggest you evaluate the app with QSDA Pro.  You will get a picture of RAM footprint for the total app and per user, plus identification of performance hot-spots and best practice recommendations. 

Use the RAM information to:
- Identify how much RAM could be saved by dropping unused fields. Use the Drop Fields tool to generate a Drop fields statement for unused fields. 
- Identify used fields that occupy lots of RAM and perhaps could be stored more efficiently. 

-Use the Viz Calculation timings to identify what charts are taking the longest to calculate and where -- what measure or expression - the time is consumed. 

-Use the Performance flags to call out practices that may negatively affect app performance. 

Video: Using QSDA Pro

The Qlik App Performance Evaluator is useful as well, but it is currently available only in SaaS.  QSDA Pro can evaluate apps in both SaaS and on-prem Qlik.

-Rob

View solution in original post

2 Replies
Frank_S
Support
Support

I suggest that you start with evaluating performance of your App using the following.

You can use the performance evaluation tool to discover detailed information about the performance of your apps and components therein. Once you have done a baseline evaluation, you can then start to compare evaluations for changes in performance against future evaluations.

 

Once you see the differences in the evaluations, you can see where the performance improved or declined based on changes made.

 

If you don't have an existing baseline to work from, you will still see performance results of individual app components.

 

From this, you can then apply the suggestions found here based on the evaluation findings.

Kind regards...

 

Please remember hit the 'Like' button and make helpful answers as 'Solution Accepted'... Cheers!
rwunderlich

I suggest you evaluate the app with QSDA Pro.  You will get a picture of RAM footprint for the total app and per user, plus identification of performance hot-spots and best practice recommendations. 

Use the RAM information to:
- Identify how much RAM could be saved by dropping unused fields. Use the Drop Fields tool to generate a Drop fields statement for unused fields. 
- Identify used fields that occupy lots of RAM and perhaps could be stored more efficiently. 

-Use the Viz Calculation timings to identify what charts are taking the longest to calculate and where -- what measure or expression - the time is consumed. 

-Use the Performance flags to call out practices that may negatively affect app performance. 

Video: Using QSDA Pro

The Qlik App Performance Evaluator is useful as well, but it is currently available only in SaaS.  QSDA Pro can evaluate apps in both SaaS and on-prem Qlik.

-Rob