Subset Report Caching

Quality Architect • MicroStrategy

Subset report or view report caching can improve dossier performance in almost 70% of all cases. Normally a cube cache stores data in memory and a subset reports based on those cubes can be quickly executed. If the cube and subset report have similar objects, a best practice is to use the cube as the dataset instead of subset report. However, subset report caching is beneficial in complex report design cases. This feature is available starting from MSTR 10.10.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
Subset report caching is beneficial in complex report design cases. For example, say a subset report execution needs to perform complex metric calculations that might take around 60-90 seconds to run against a cube. In this case, enabling the subset report cache will improve dossier performance.
Subset report caching can be used for OLAP and super cubes.

How to Enable Subset Report Caching

In Strategy Developer, open the report in the Report Editor.
Choose Data > Report caching options.
Select Enabled: This report should be cached.
Click OK.

For other caching options, see Caching in the Advanced Reporting Guide.

Subset Report Cache and Report Service Document Execution

Generating the DFCCubeInfo during a document's execution can often be time consuming and impact the document's performance. With a subset report cache, the DFCCubeInfo is cached there so it does not need to regenerate when a document is executed.
The DFCCubeInfo in the subset report cache is not persisted to disk. It is generated during run time and is available in-memory as long as the cube cache is loaded in-memory because the DFCCubeInfo depends on project schema, which gets refreshed each time the server is restarted.

Subset Report Cache Workflow

All governing and related cache settings that apply to normal report caches apply to subset report caches.

1. Generate the cache.

When the subset report is executed alone, the subset report cache is generated without DFCCubeInfo.
When the subset report is executed inside document services, the subset report cache is generated with the DFCCubeInfo.

2. Hit the cache.

When the DFCCubeInfo is not cached:

Execute the subset report alone > hit cache.
Execute the subset report inside a document or dossier > hit cache and generate DFCCubeInfo and cache it.

When the DFCCubeInfo is cached:

Execute the subset report alone > hit cache.
Execute the subset report inside a document or dossier > hit cache.

3. Invalidate the cache.

Invalidate the subset report cache in the following cases:

Republish
Incremental Refresh
Delete

4. Update the project scheme to clear the DFCCubeInfo.

Examples of Test Results with Subset Report Caches

The test results below are from a customer's dossier that uses one normal report dataset and one subset report dataset.

Response Time for a Single User Test

Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB
Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB

RSS Peak Usage for a Single User Test

Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB
Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB

Average Response Time for 10 User Concurrency Test

Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB
Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB	Detailed logs. Might create multiple large log files. 1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB

Growth of RSS Memory Usage for 10 User Concurrency Test

Detailed logs. Might create multiple large log files.
1st Response Time2nd Response Time3rd Response TimeWithout Subset Report Caching163 seconds53 seconds53 secondsWith Subset Report Cachine166 seconds35 seconds34 seconds 1st Peak Growth of RSS Memory 2nd Peak Growth of RSS Memory 3rd Peak Growth of RSS Memory Without Subset Report Caching4845 MB2457 MB104 MBWith Subset Report Cachine4161 MB9 MB90 MB Average Response TimeMinimum Response TimeWithout Subset Report Caching146 seconds84 secondsWith Subset Report Caching62 seconds44 seconds Growth of RSS MemoryWithout Subset Report Caching41438 MBWith Subset Report Caching19885 MB

KB483046

Comment

0 comments

Details

Knowledge Article

Published:

March 27, 2019

Last Updated:

March 21, 2024

Subset Report Cache and Report Service Document Execution

Subset Report Cache Workflow

All governing and related cache settings that apply to normal report caches apply to subset report caches.

1. Generate the cache.

When the subset report is executed alone, the subset report cache is generated without DFCCubeInfo.

When the subset report is executed inside document services, the subset report cache is generated with the DFCCubeInfo.

2. Hit the cache.

When the DFCCubeInfo is not cached:

Execute the subset report alone > hit cache.
Execute the subset report inside a document or dossier > hit cache and generate DFCCubeInfo and cache it.

When the DFCCubeInfo is cached:

Execute the subset report alone > hit cache.
Execute the subset report inside a document or dossier > hit cache.

3. Invalidate the cache.

Invalidate the subset report cache in the following cases:

Republish
Incremental Refresh
Delete

4. Update the project scheme to clear the DFCCubeInfo.