In QlikView, applications are much slower to open immediately after a reload than when they have been previously opened. The preload option is checked but it is having no impact.
Preload will not be triggered automatically after the Reload has been done. Those are not synchronized, this is working as designed.
The design is that the application will be cached into memory either:
- Every 10th minute
- When a user opens the application and a Reload has been done but the preload hasn't been triggered yet
- A user uses the application while a new Reload is performed
It is possible to add a setting to Settings.ini and choose how often the preload will be performed. It is not possible to set on document level, it will apply for all documents which has Preload defined.
Setting to add in Settings.ini: QvMetaInterval=[time in minutes] i.e ‘QvMetaInterval=5’
If QvMetaInterval is set to 0, preloads are performed every time the folders are scanned. QvMetaSecondsToWaitBetweenScans (Default value is 60 seconds) tells how often the folders should be scanned.
Those need to be added in the [Settings 7] section of the QlikView Server settings.ini file (C:\ProgramData\QlikTech\QlikViewServer). It the environment is a cluster, it will need to be added on each node holding a QlikView Server service.
Please note that a too high frequency for the preload may have an impact on performance
and will need to be adjusted depending on your environment.