Qlik Community

App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Announcements
Now Live: Qlik Sense SaaS Simplified Authoring – Analytics Creation for Everyone: READ DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
DevelopCal
Contributor III
Contributor III

dashboards performance

Hello

 

We´re having some problems with the dashboard performance.

one of the reason could it be the calculations in the script?

i mean, if the Amazon Web Services data could have this calculations instead of dashboards, could it run better?

 

thanks!

Labels (1)
2 Solutions

Accepted Solutions
avinashelite

Which Performance your talking 

1. Dashboard front end response ?

If Yes, then you need to check your

* Data model  design

* Data volume

* Any calculated dimension in the frontend etc

2. Reload time 

* Depends on the transformations

*Data volume 

*  RAM availability etc   

View solution in original post

marcus_sommer
MVP & Luminary
MVP & Luminary

Each selection will cause a new calculation of the selection states and of all visible objects unless Qlik could apply already cached results.

If the responses within the UI are too slow you need to review the UI calculations (especially avoiding nested if-loops, aggr-constructs and interrecord-functions) and the datamodel which should be developed within the direction of a star-scheme.

- Marcus

View solution in original post

3 Replies
avinashelite

Which Performance your talking 

1. Dashboard front end response ?

If Yes, then you need to check your

* Data model  design

* Data volume

* Any calculated dimension in the frontend etc

2. Reload time 

* Depends on the transformations

*Data volume 

*  RAM availability etc   

DevelopCal
Contributor III
Contributor III
Author

It takes to much time when we delete a selection of a filter and we choose another value in this filter.

is there any trick for don´t calculate until you choose another value? thanks!

 

marcus_sommer
MVP & Luminary
MVP & Luminary

Each selection will cause a new calculation of the selection states and of all visible objects unless Qlik could apply already cached results.

If the responses within the UI are too slow you need to review the UI calculations (especially avoiding nested if-loops, aggr-constructs and interrecord-functions) and the datamodel which should be developed within the direction of a star-scheme.

- Marcus