Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

What use case will benefit from this improvement?

In Strategy 2021, we introduce a new cube type called Attribute Form Caching cube. This cube can be used to improve the performance for normal report execution that run against databases, Intelligent cube publishing and connect live to project dossier execution. Refer to Product Manual for more detailed information.
We did internal performance test for both report execution and cube publishing. It improves 30% performance in average.
 

What parameter could affect the scale of the improvement and how?

The Attribute Form Caching cube caches Attribute non-ID Forms(e.g. NAME Form in Attribute Customer) to save data fetching time from databases for attribute non-ID forms.

• The more row of data are caches in the Attribute Form Caching cube, the more improvement for the performance.
  
• The more Attribute Non-ID Forms are cached in the Attribute Form Caching cube, the more improvement for the performance.
  
• The data type for the Column used in Attribute Non-ID Form also affects the improvement. The larger data size is for the column, the more time is needed for data transfer, the more improvement is made for the performance.
  

The additional cost is to create and publish a new Attribute Form Caching cube, which is one time work and also additional cost for memory.
 

Are there any exception situation that could cause no benefit?

The feature does not support the following:

1. Subset Report
2. Incremental Refresh Report against Intelligent cube*
3. Datamart Report
4. Report/cube attributes only contain ID form

Enhancement*

In Strategy 2021 Update 2, Incremental Refresh Reports are supported to dynamically source its attribute form(s) data from the Attribute Form Caching Cube.