Troubleshooting Template Performance Issues

Template loading speed is affected by many factors. If a template loads slowly during preview, use the methods in this document to identify the cause.

Checking Dataset Query Speed

Most templates load slowly because SQL queries are time-consuming. You can use the following methods to check the SQL execution speed.

1. You can query the dataset directly in the designer to assess the speed. If the query is slow in the designer, consider replacing the database driver.

2. You can export the template as one with built-in datasets and preview the template to see if the loading speed improves. If the exported template with built-in datasets loads faster during preview, the issue is likely caused by slow data retrieval. In this case, optimize SQL statements or database performance.

If the template loads slowly because SQL queries are executed too many times, try enabling the Extracted Data Cache function.

3. You can enable the Extracted Data Cache function and see if template loading speed improves. If the template loads faster after the cache is enabled, the issue is likely caused by poor dataset query performance.

Checking the Template Structure

After ruling out SQL-related causes, check whether the template is overly complex or improperly configured. The following sections describe common improper settings.

Too Many Filters

As shown in the following figure, the first column is manually entered, while the remaining fields are repeatedly dragged in, each with a filter applied. The example template is relatively simple. In practice, however, templates with this structure are often much more complex and can cause extensive redundant calculations that affect performance.

Too Many Condition Attributes, Filters, Dynamic Parameters, or Display Settings

If you see many yellow, blue, or red triangle indicators in a template, it means the template uses many filters, conditions, or widget settings, which will inevitably affect performance.

Improper Parent Cell Settings or Cartesian Products

You can resolve issues of this type by modifying parent cells and optimizing template structure. For details, see Prevention of Cartesian Products During Submission.

Large Images in the Template

If a template includes large images or many images, performance may be affected. You can consider using the WEBIMAGE function for image display.

Too Many Cells During Template Preview

When the data volume is high or the template structure is complex, many cells are generated during backend template calculation, and frontend display is also slow. Therefore, reduce the amount of data displayed in a single preview or consider using SQL pagination or the new calculation engine.

Too Many Charts

Using too many charts can slow frontend rendering and even cause the browser to crash. Therefore, do not overuse charts when designing templates.

Improper Use of Functions

If a template uses many functions, such as SQL, VALUE, or dataset functions, or if any SQL function runs slowly, the template preview may slow down.

Frontend Style

Extensive use of JavaScript (JS) or Cascading Style Sheets (CSS) statements to modify template element styles can affect template performance.

Global Parameter

Global parameters are loaded when the page loads, regardless of whether they are called, which affects template loading speed.

Global Watermark

Check whether the SQL function is used in global watermark settings for data retrieval. If the SQL function cannot retrieve data or retrieve data slowly, all templates must wait for the function to time out before they can be displayed. As a result, template previews become slow. You can disable global watermarks for testing.

Sheet Name

Check whether the sheet name is a fixed value or a formula. If it is a formula that involves parameter value calculations, template calculation speed may be affected.

In this case, you can change the sheet name to the default value for troubleshooting.

Slow Calculation of Default Parameter Values in Button Widgets

Default parameter values in button widgets are calculated when the template is initialized, not when the button is clicked. If a button widget calls many SQL functions and the calculation takes a long time, template loading speed may be affected. For example, if a button used to reset all widget values calls many SQL functions to calculate default widget values, template loading speed may be affected.

Blank Row

Blank rows in a template may also affect template loading speed.

Page Background

Check the page background settings of the template. Do not set an excessively large page size, and note that using a textured background may affect template performance.

When issues of this type occur, you can adjust the page size or change the page background.

Checking Network Requests

1. Press F12 in a browser and open the Network tab to view all template requests and their response time. Then check whether any request takes too long and identify its purpose.

2. On the Network tab, check the waterfall area for requests that take a long time. Select a request to view the duration of each request phase. If a request takes too long, first check whether the issue is caused by mapping.

3. The Size column shows whether related resources are read from the disk cache. Resources read from the cache generally do not affect performance.

1. Log level

Lower the log level. For example, you can change it from DEBUG to ERROR.

 2. Whether the external database is used

Performance of the built-in database is limited. You can consider using an external FineDB database.

3. Adjust the thread count of the middleware (such as Tomcat) and the connection pool of the business database based on the number of concurrent requests.

4. Disable Always Re-read Template in Extracted Data Cache on the decision-making platform.

5. If the template loads slowly only on the first access, you can consider enabling the Extracted Data Cache function to optimize template performance.

Template loading goes through phases such as data retrieval, calculation, and rendering. Factors in each phase may affect loading speed, so you need to troubleshoot performance issues phase by phase. During troubleshooting, reduce template elements as much as possible to identify the part with the greatest impact on performance.