Response time was very long from accespoint Qlikview each morning monday

[syl2bri]

Hi 

we have many user complaints each monday morning  when user consult Published reports ,

We are in QV 12.4  

Have idea to avoid theses problems ?

we have a QVS physicaly server (2 T memory ) an other server (Publisher server ) and in last a VM where IIS components is installed ,

Could we have some configurations parameter betweenn servers QVS end IIS Server

Have you another idea to manage  users ,

Manys users exports in excel whit big  data volume from access point

How you can identify botleneck ?with what tools

Do you recommend to purge shared file objcets on qvw application

Have you other idea  ?

Thanks

Regards

[marcus_sommer]

I think you should at first monitor the usage within your environment before you could make any deductions which measures may improve the situation. To start with it you could implement the governance dashboard which is a special meta-data tool which you could download from the Qlik download area.

Beside this your environment might not be suitable sized. If for example 90% of all the usage happens on the Monday morning you may then need more RAM/CPU and nearly the complete other time you may have much unused resources. But there is no perfect solution ...

Further you should look if the server might be re-started regularly during the weekend and lose with it all the caching. Just for QlikView it's not necessary ... In such cases you may benefit from pre-loading the applications into the RAM before the first user access happens (there is an appropriate option within the qmc).

- Marcus

[Chip_Matejowsky]

Hi @syl2bri,

Could you clarify a bit more where the performance issues on a typical Monday are experienced?  During the reload/distribution of QVWs?  When your end users are attempting to open QVWs from the AccessPoint?  Please be as specific as you can.

If on the QVS/AccessPoint side, I agree with Marcus' great suggestions.

If on the QDS/Publisher side, the Qlik whitepaper Scaling the QlikView Publisher attached to the preceding hyperlink does a great job of detailing potential QDS/Publisher potential performance bottlenecks.  So highly suggest that you read it.

Best Regards

[syl2bri]

Thanks for your return 

Ours problems is not on QDS ,but between server QVS en IIS Qlik server 

Botleneck im mainly monday when there is an intense concurency access

i know some  part of  governance dashbord but not all ;you have detail about QDS load but not on QVS access and mainly response time but we have Dynatrace for tthes response time

Memory QVS this morning increase until 1,7 Tera 

Could you help me about  applications and in detail complexity  part of goverance dashbord 

What is relevant indicator in goverance dashboad

Thanks in advance

[marcus_sommer · Accepted solution]

I suggest to check at first the (for each server and services) available RAM resources and their consumption - on Monday but also on the other days (because you will need these information to evaluate the behaviour against the normal usage). If there isn't enough RAM available the services will use the virtual RAM on the disc and this could slowdown the performance quite heavily.

The governance dashboard displayed a few key-features from the QVS and you may also look directly in the log-files and maybe adjust/extend the views within the dashboard. Further thinkable is to go a step ahead and querying the windows performance monitor:

QlikView - How to log CPU, Disk, and memory usage ... - Qlik Community - 1712237

Also contained the governance dashboard the possibility to look within the application-usage (audit-log) and to see what the users are doing (depending on your country and your company rules there may restrictions about this kind of data).

You mentioned that the users are using Excel exports quite extensively. For such tasks is no tool designed and really performant - also not Qlik. If the users are exporting tables with hundred thousands of rows by dozens of columns the calculation times and the RAM consumption could become quite high - whereby the QVS is here the slightest problem because the rendering and exporting is then executed from the web-server and here your IIS may have not enough resources for it.

For a regular export of such amounts of data you may better provide these data directly for the users during a nightly timeframe.

- Marcus

[Chip_Matejowsky · Accepted solution]

So for performance issues on the QVS side, ensure that your QMC > System > Setup > QlikView Servers > QVS@ > Folders tab > Mounted Folders only contain QVW files and no other file types.  If you currently have your QVW files in the Root folder, overhaul the folder structure so that only PGO files are stored in the Root folder and you have .QVW files in Mounted Folders.  This is important as QlikView scans all files when loading the AccessPoint. 

To Marcus' previous post, consider preloading the most heavily used QVW files so that they are already in memory when users begin to access them. The preload option for a document can be configured in QMC > Documents > Source Documents > Name of QVW > Task name > Server tab > Performance tab > Preload checkbox.

Regarding your questions about the QlikView Governance Dashboard, start with What is the Governance Dashboard? and read through the entries listed on the  left side.

Best Regards