Association Acceleration

Version

Application Scenario

After association establishment for multiple tables in Model Center, when you perform cross-table analysis for fields within the tables, you can enable acceleration and click Submit to trigger a cache update for pre-calculation, thereby improving the calculation efficiency of field usage.

The following example consists of two dimension tables and a detail table. You can use Product Sales Details as the base table and add the two dimension tables to this table to perform association acceleration. Then, you can use the Sales Amount field in the detail table to add the cross-table calculation. In this case, you can realize acceleration.

1. Click the Acceleration Management tab on the left to enter the Acceleration Management page, as shown in the following figure.

You can view the resources configured with association acceleration and information such as the storage size and acceleration. You can also modify the information.

2. Click Create Association Acceleration, and create an association with Product Sales Details as the N-end table and the two dimension tables as the 1-end table, as shown in the following figure.

Note:

Selectable resources for Add Acceleration Resource to Accelerate: all 1-end tables pointing to the selected table in the association model, excluding tables with 1:1 associations or those associated via a 1:1 path.

3. After completion, click Submit to trigger the acceleration.

4. You can refresh the page to view the acceleration status, or click the  icon to view the update status of the acceleration task in Association Acceleration Update Info, as shown in the following figure.

1. N: N and 1: 1 table associations are not supported.

2. The 1-end table data of table associations cannot be duplicate.

3. The maximum column limit for associated cache updates is 200 columns by default. You can modify the limit through the FINE_CONF_ENTITY Visualization Configuration plugin.

Parameter Description:

Suggestion on Parameter Modification

You are not advised to set an excessively large column number for associated cache updates, as the performance burden may be increased.