Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I have noticed the first time I run an On-Demand Pixel Perfect Report the run time could be about 2 minutes. This is a large report with about 20 pages.
The second time I run the report it is around 30 seconds.
Is there a way to improve the performance the first time the report is run?
Thank You,
Michael
Hi,
Performances depend on many factors. Refer to the page https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/Performance.htm...
Generation time also depends on the structure of the report. For example, multiple nested levels will increase it.
I also suggest you monitor the Qlik Sense server workload during reports generation and avoid using section access (that is supported) but use native Qlik NPrinting filters instead.
Best Regards,
Ruggero
Hi @mstoler
I believe it is because of cache benefit and loading app to the memory . I dont think you can do much about it. I will say that this goes down to well known roots of how Qlik engine works
Hello @mstoler ,
When you execute a task or request an on-demand report NPrinting starts to open connections to qlik app (min 1 and max, by default, number of core of NPritning server) once at time, it doesn't open all available connections at start. After complete the request NPrinting doesn't close them, so when you request a second report NPrinting has some connection open.
You can monit the allocation of resolver at this hidden link of nprinting console https://nprintingserver:4993/#/admin/plan
The rightest columns with four exadecimal digits identify the last digits of NPritning Engine, for each of them you could see how many connections are open on each of avilable engine. When you see a blue number means that np is opening a connection, instead yellow means np is closing a connection.
Hi,
Performances depend on many factors. Refer to the page https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/Performance.htm...
Generation time also depends on the structure of the report. For example, multiple nested levels will increase it.
I also suggest you monitor the Qlik Sense server workload during reports generation and avoid using section access (that is supported) but use native Qlik NPrinting filters instead.
Best Regards,
Ruggero
Thank You.
It takes about 3 minutes the first time.
The second time it drops to about 30 seconds.
Michael