Common Symptom:
- Less the sufficient performance
- Connections fail to generate in NPrinting
Environment
Resolution:
How to Improve NPrinting Connection Generation Performance and Mitigate Connection failures:
- Copy, then reduce the QVW or QVF to a data set necessary for generating reports, i.e. such that it is *500 mb or less for example.
- Remove any charts or other unnecessary for reporting purposes. This will also reduce the size of the QVW or QVF.
- Remove any alternate states, triggers - sheet and document, and the list box property 'only one selected', Variables using as selection values/critera on the QV desktop as well as Input Boxes. (These items are NOT supported with NPrinting On Demand)
- If the reporting QVW or QVF contains several containers, remove any reporting charts from the containers.
- Follow QlikView and Qlik Sense app design best practices
- ie: move complex calculated dimensions and expressions to the load script where possible.
- Remove unsupported items
Specific to QlikView:
- Try connecting to the document directly instead of via QVP. Performance may be improved with a direct connection. Keep in mind that doing so will require that you schedule/trigger regular NP connection reloads to ensure you have the most up to date data.
- (Note: do not take this step with On Demand Connections. QVP is required for NP On Demand reporting).
- Ensure that the NPrinting Engine Computer is sufficiently provisioned with RAM and CPU to be aligned with the scale of usage. If RAM and CPU are maxed out regularly, please add these resources as needed
*500 MB is just a reference value. Performance may vary depending on actual machine resources and complexity of the QVW or QVF document/application.
Related Content
