Another area would be the number of charts and objects on the screen when the selection is done.
Due to the way ajax works, it will not be as performant as the plugin. It seems that compared to the plugin, the Ajax client requires more of the data to be returned before the objects and charts can be rendered. Depending the complexity of the sheet, this can add up significantly.
Could cacheing explain some of the differences?
You make a new set of selections on a machine and the selection takes 15-30 sec as the selections are new and not cached; when you then test the same selections on another machine, the results are delivered from the cache so appear faster.
What version of QlikView are you using?
Is the slow performance related to table charts that display a large number of rows?
thanks all for the replies.
I just had a remote session with the customer and I performed some tests.
As stated from Albert, I suspect the time differences in the response time were in fact that Qlikview has cached the result set.
Indeed the main issue of the slow response time is depending on the number of UI obeject displaying on the sheet.
I have tried to remove for testing purpose different charts and the performance were good. Thanks to Know Chong for the hint.
The original sheet has many different UI objects (pivot table, straight table, graphs and so on) which are hided and displayed using variable depending on the need of the enduser
I have a question regarding the calculation of each chart:
- Is the calculation be done also when the charts are hided?
- Instead if I minimize the objects it could help me to improve the response time, as I understood the calculation will be not performed for minimized objects....is that truth?
- What could help me to improve the performance ?
Thanks to all for the help!
I appreciate very much!
You can add calculation conditions to charts, so that the chart does not calculate until the conditions are met.
e.g. Count of rows < 20000 or Count(Year) < 3, or the relevant chart variable is enabled.
The calculation condition is on the chart properties, General tab.
You can also customise the Error Message for the calculation condition.
Hidden and minimized charts are not calculated.
Use Document Analyzer (http://qlikviewcookbook.com/recipes/download-info/document-analyzer/) to identify which charts are taking longest to calculate. That will give some focus and objective measurements to your tuning efforts.