NPrinting: reduce task execution time and work with large QlikView documents

The NPrinting performance depends on many factor: how big the QlikView document is, the complexity of the reports, the machine hardware etc.

There are some suggestions you can follow to improve the NPrinting performance, especially if you are working with large QlikView documents.

It is very important to be able to generate report quickly, especially for the user that are working with On-Demand.

To generate an NPrinting report, it is possible that you could have multiple NPrinting filters and thus multiple selections cycling potentially through some, several or all values of a dimension as well as complex QV Charts and chart expressions within a large QVW.

In this case, significant hardware resources would be needed on the QVW server to support the large QVW size so that QV can parse the data in the QVW quickly in order to generate an NPrinting Report.
If the QVW file size is smaller, these iterations could be much quicker as the "selections" process would not have to iterate through vast quantities of historical data
So in the case of large QVWs approximately 1 GB and Higher, it would be a good practice to reduce the QVW to a more manageable size and only for the data set that you need to report on.

You can use the reduce feature in NPrinting to reduce the QVW to a more manageable size

If you have QlikView Publisher, you can use that as well to reduce your QVWs to a leaner, more report friendly size.

One of the most popular and efficient alternatives to reducing the QVW is to create a Binary Load QVW that is binary loaded to a Primary QVW. This Binary Load QVW would only contain the charts that need to be reported. A leaner QVW for reporting purposes results in faster On Demand report processing from end to end.

There are other tricks that may help you to get a better result:

1. Minimize all the table and charts that are not used in NPrinting.
NPrinting opens QV in a graphical session so all the tables and charts that are not minimized must be calculated. This requires time.
So keep maximized only the objects that are used in the reports.

2. Sometimes the calculations you are using in the dimensions can be moved to the script.
Please, do this whenever it is possible.
Calculations in the Expressions will be calculated only once during the reload and not at every selections.