Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Look here for ways to do optimized qvd loads
https://www.quickintelligence.co.uk/qlikview-optimised-qvd-loads/
You can replace most of your left joins with mapping.
Didn't call all the mapping tables here in the example but you call them at their appropriate places and check if the load time gets reduced. I am sure still there is room for more optimization.
Hi,
Script Level:
* Hold the synthetic keys to a minimum. Remove unnecessary links and joins tables explicitly in the script.
* If a reloads takes a great deal of time, use a binary load of static historical data.
* Drop tables from memory in the script once they have fulfilled their role.
* Use the AutoNumber() function to create a compact memory representation when using a complex composite key.
UI Level (layout):
* The memory used by objects and calculation times can be maintained in the sheets tab of the document properties. A good way to find bottlenecks in the application.
* Minimized charts do not take up memory. Uses the auto minimize option with charts that do not need be displayed at the same time.
* Force the user to make a selection before a large chart is displayed to reduce chart calculation times.
* Use appropriate messages while charts are being calculated.
* Avoid long expression with multiple string comparisons.
* Avoiding showing frequencies in Listboxes where not necessary.
PFA....