DataManager takes long to load/open

[pwagner]

Hello,
our customer created an app with the data manager (roughly 200 MB big). All of the script is created with the data manager, so it's important that the data manager work properly.
 
Unfortunately it takes minutes to open up the data manager with all the tables (15).
 
Here is the time how long it takes in average:
Robert 2:46 Min (directly after a reload)
Robert 0:51 Min (data already existing in app - no reload)
 
Alina 2:45 Min (directly after a reload)
Alina 1:05 Min (data already existing in app - no reload)
 
Jakob 0:45 Min (directly after a reload)
Jakob 0:46 Min (data already existing in app - no reload)
 
Do you have any idea why the data manager takes so long to open? 
Do you have any recommendation to decrease the time of loading of the data manager? 
Should we check the data connections?
 
Thank you.
Best regards,
Patrick

[Frank_S]

Have you check the System Resources of the computer that see this performance problem? Does the Qlik Sense server have sufficient system resources?

Are there a lot of calculated dimensions in the QVF? 

• Add hardware and cpu resources to the QS and or Desktop that is performing the tasks
• Check the QVF for performance enhancement possibilities. (moving as much to the load script - ie: calculated dimensions) as possible will dramatically improve performance.)

Just a couple of things to check

[marcus_sommer]

I think checking the data connections is a good starting point. It's not really the same but the logic behind it might be similar - if in View are multiple data-base connections are included the opening of the script-editor takes significantly more time as without them - probably because the appropriate *.dll's and the configurations are loaded in an early binding and not just to the run-time.

Another point are various centralized information in Sense like the file-connections, master-items and similar stuff and also more or less granular set security settings. This may be different by the users and each of them will need some time - maybe also some (fixed) waiting-times by repeating the tasks n times (to avoid errors).

Beside this the data-set by reloading and/or opening might be different for the users, for example caused by any section access.

- Marcus 

[pwagner]

Thank you @Frank_S and @marcus_sommer  - We will check it.