Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

cancel
Showing results for 
Search instead for 
Did you mean: 
podge2019
Contributor III
Contributor III

nPrinting Max Number of Tasks

Hello,

Just a quick query on as I cannot find the details online.

We have an app that has grown legs. Initially it was 5 Publish Tasks to send password protected PDF's externally and now this number of tasks has grown to over 100.

Each month QlikView is loaded with a report and some months there will be no data for certain clients.

Some people were not happy with having to select multiple individual tasks so as a workaround we have now embedded a variable in the body of the email. On the settings on nPrinting under task we have it set to "Do not send the email" when a publish task cannot resolve a variable tag.

This then meaning that if there is no data in QlikView for nPrinting to pick up nothing happens...only a failed task in nPrinting.

So to the question part...is there a maximum number of tasks that can be run in nPrinting at once at the same time?

The idea being that the end users can just hit select all at the top and these 100 or so tasks will all run at the same time and only produce emails with attached reports when there is data there to produce it.

Thanks very much.

Qlik NPrinting 

Labels (2)
2 Solutions

Accepted Solutions
Lech_Miszkiewicz

Number of task running is dependent on number of cores on engine server and total number of engines. Nprintin IP is not common knowledge so we will never known the logic used to trigger and run tasks, however it depends on number of cores and engines. On top of that number of cores per engine in QlikView configuration should not be greater than 12 or 16 (check the exact number on https://help.qlik.com documentation).

The idea to run everything at the same time will not work as there is still bottleneck in Qlikview<-> Nprinting communication.

I think the maximum optimal/possible per engine would be that number between 12 and 16 , but it is not guarantee since NPrinting algorithm can still decide differently!

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.

View solution in original post

Ruggero_Piccoli
Support
Support

Hi,

There are not built in limitation on the number of users in a task, or the number of reports etc. The Qlik NPrinting Scheduler will optimize the reports creation based on the resources you give to Qlik NPrinting and the answering time from Qlik View or Qlik Sense sources.

You can create the task and monitor the time needed to deliver the reports and the usage of the hardware and in case increase it.

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

5 Replies
Lech_Miszkiewicz

Number of task running is dependent on number of cores on engine server and total number of engines. Nprintin IP is not common knowledge so we will never known the logic used to trigger and run tasks, however it depends on number of cores and engines. On top of that number of cores per engine in QlikView configuration should not be greater than 12 or 16 (check the exact number on https://help.qlik.com documentation).

The idea to run everything at the same time will not work as there is still bottleneck in Qlikview<-> Nprinting communication.

I think the maximum optimal/possible per engine would be that number between 12 and 16 , but it is not guarantee since NPrinting algorithm can still decide differently!

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.
podge2019
Contributor III
Contributor III
Author

Thanks @Lech_Miszkiewicz  fountain of knowledge as always 😀 much appreciated. Back to the drawing board.

podge2019
Contributor III
Contributor III
Author

Hi @Lech_Miszkiewicz  thinking as a workaround....do you think one task with over 100 users, in one group, would be possible?

If I add Passwords at a user level, add a filter to the users and then add them to the task would it be okay?

The task would just have one report that wouldn't cycle, filters would just be applied at a user level?

Tested with adding 3 users there and it appears to do the job....just wondering with over 100 in a group added to a task would it be okay.

Our set up is Single Engine, 4 Cores and 24GB of RAM.

Ruggero_Piccoli
Support
Support

Hi,

There are not built in limitation on the number of users in a task, or the number of reports etc. The Qlik NPrinting Scheduler will optimize the reports creation based on the resources you give to Qlik NPrinting and the answering time from Qlik View or Qlik Sense sources.

You can create the task and monitor the time needed to deliver the reports and the usage of the hardware and in case increase it.

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.
Ruggero_Piccoli
Support
Support

Hi,

In your scenario you could also evaluate to use conditions. Refer to https://help.qlik.com/en-US/nprinting/May2021/Content/NPrinting/ReportsDevelopment/Conditions.htm.

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.