Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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!
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
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
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
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!
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