Slow Export Troubleshooting for Templates with Large Datasets

This document describes how to troubleshoot slow export issues for templates with large datasets.

Procedure

Checking the Export Request

There are two types of export requests:

• Requests that include the sessionID parameter

• Requests that include the template name, for example, ?viewlet=a.cpt&op=export&format=pdf

For requests of the first type, data is not retrieved or calculated again, because the calculation has already been completed during preview. Requests of the second type, however, do require these steps. Therefore, if a second-type export request takes too long, first review the info log and check the SQL execution time to determine whether data retrieval is the bottleneck. For details, see Troubleshooting Template Performance Issues.

Checking the Database Driver

For an SQL Server database, earlier versions of the JDBC driver (sqljdbc) may cause performance issues. Upgrade the driver to sqljdbc42 to resolve the issue.

Checking the Template

Chart

Issue description

If the template includes charts, the slow export issue may be caused by the absence of J2V8 on the server. Without J2V8, the system falls back to Nashorn, which delivers lower performance.

Solution

Upgrade GCC. For details, see Upgrade Description of Chart Export.

WEBIMAGE Formula

Issue description

The WEBIMAGE formula is used in the template, and its parameter is set to your own service address rather than a directly accessible image URL. If the service responds slowly, the export slows down as well, and template previews can also be slow. In this case, check the performance of your service.

Solution

Remove the formula from the template, export the template again, and compare the export speed.