Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
mstoler
Partner - Specialist
Partner - Specialist

pixel perfect on demand performance

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

Labels (1)
1 Solution

Accepted Solutions
Ruggero_Piccoli
Support
Support

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



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.

View solution in original post

4 Replies
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

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

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
andregas
Partner - Creator II
Partner - Creator II

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.

 

Ruggero_Piccoli
Support
Support

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



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
mstoler
Partner - Specialist
Partner - Specialist
Author

Thank You.

It takes about 3 minutes the first time.

The second time it drops to about 30 seconds.

 

Michael