Looking for ideas to optimize a QlikView reload task

[bertrand_herard]

Hi,

on a QlikView Server 11.2 SBE (without Publisher), I'm trying to optimize the reload of a QlikView File (which is frequently reloaded). Is anyone know what QlikView does in the following part of the task ? (and know how to accelerate it) :

(2015-04-03 10:58:43) Information: Reloading

(2015-04-03 10:58:50) Information: The Source Document reload complete. DocumentPath=E:\QLIKVIEW\APPLICATIONS\PPD\INTERFACE\NUX\NUX.qvw

(2015-04-03 10:58:50) Information: Memory Allocation Delta for this file=178.04 Mb. Available Physical Memory Before Reload=21454.67 Mb. Available Physical Memory After Reload=21292.73 Mb. Total Physical Memory=21292.73 Mb.

(2015-04-03 10:58:53) Information: Reloading.

(2015-04-03 10:59:03) Information: Reloading..

(2015-04-03 10:59:04) Information: The Source Document was reloaded successfully.

Details : my tasks last 1 min 25 s while the reload last only 34 s. Looking in logs, I found that the 1min34s can be split like this :

2 s : QlikView task initialization and start (OK)

9 s : Opening QlikView File (OK, if someone have tips to accelerate It, I'm interesting in).

34 s : QlikView File reload (OK)

20 s : don't know what's QlikView is doing and that's my main question (in my example above the QlikView reload is finished at 2015-04-03 10:58:44)

19s : saving file (OK)

1s : closing QlikView Reload task (OK)

Regards

[Gabriel]

Hi,

When QlikView finished reloading, it has to build the Data Model. The process of building the Data Model sometimes takes time depending on the number of joins / associations QlikView has to create.

If it takes long to then you need to look at your code and see how you can optimized your application.

As there's no QVW file attached, there's no way to suggest how to optimized your application. However, there are several way to do this. If you need further suggestions from community post sample file.

Hope this is helpful

[p_verkooijen]

Set Compression to none (Document Properties)

It saves time opening and saving the document.

Also is this a dashboard or a script generating QVD's ?

If it's only for generating data you should drop all tables.

[Anonymous]

do you have so many joins keeps synthetic tables circular references etc ?

do you have section access getting loaded after the script which is complex ?

what is the server configurations ?

what is the physical size of the file ?

it would be great if you can generate log file and share it for better understanding

[sujeetsingh]

Please follow this

Best Practices for Data Modelling