Hello All once again,
In my last article we have gone through Server and Scripting side techniques for optimizing QlikView application. If you have missed it, please hit this link, and get to know some exciting tips on same. In this blog post, we will check the optimizing techniques at Design side.
Design side means the configuration side of the QlikView. Below are few tips which you can try out -
Monitoring Memory Consumption at Object Level:
Memory utilised by the QlikView objects and the calculations time can be monitored from the document properties. This will helps to identify which object is consuming more memory and finding the reason for delay in loading time of the QlikView application.
Minimised Chart Vs Maximised Chart:
Minimized chart objects will consume less memory
comparing to the maximized one, hence use of auto minimize option will be a good
practice in this case. Screenshot showing Maximized Chart consuming memory more than the
Minimized chart:
- If the chart is too large, then implementing forced selection by the user will minimize the chart calculation time.
- Showing frequencies in listbox can be avoided if not necessary.
- During sorting, it is recommended to sort numerical fields numerically than alphabetically.



No comments:
Post a Comment