Strategy ONE

Page Cache Generation

A page cache is generated in the following cases:

On-the-fly:

  • When you open a dashboard from MicroStrategy Library, if there is no valid cache, a page cache will be generated on-the-fly.
  • When you switch pages on a dashboard, a page cache for the corresponding page will be generated on-the-fly.
  • If you perform any analytical manipulations in a dashboard, such as filtering, sorting, or drilling, the Intelligence Server will stop generating page caches on-the-fly for the affected pages.

    Affected pages include pages that contain targets affected by the manipulations. For example, if you exclude an element from a visualization, the page holding that visualization is the only affected page. However, if you change a selection from the chapter level, all pages under that chapter are affected. In this case, the Intelligence Server will not generated new server caches when you switch to the affected pages.

    Manipulation Affected Page
    Switch pages None
    Link to other pages from images or text None
    Keep only or exclude on a visualization Current page
    Filter visualizations in the same page Current page
    Go to targets from a visualization Current and target pages
    Change chapter level filter panel All pages under the same chapter
    Drill on the page Current page
    Sort on a grid or visualization Current page
  • If you click the Rest button from the dashboard title bar or from the dashboard cover in Library, a page cache will be generated on-the-fly.

When closing a dashboard

When you close a dashboard and return to Library, the Intelligence Server will generate page caches for the current page and several pages before and after the current page, if there are no valid page caches. By default, at most 10 page caches will be generated.

When adding or updating a bookmark

When a bookmark is created or updated on an existing bookmark, the Intelligence will generate page caches for the current page and several pages before and after the current page, if there are no valid page caches. By default, at most 10 page caches will be generated.

When logging out of Library or if the user session times out

When you log out of Library or the user session times out, the Intelligence Server will generate page caches for the dashboards that are active in the server message. For each dashboard, the Intelligence Sever will generate page caches for the last viewed page and several pages before and after the last view page, if there are no valid page caches. By default, at most 10 page caches will be generated.

Server message refers to the last several dashboards that were ran from Library before logging out or the session timing out. The number of server messages is defined per user session and is restricted by the working set limit. The working set limit can be configured via MicroStrategy Web Preferences.

By cache update subscriptions

Cache scheduling is supported by Distribution Services. You can create a cache subscription for a base dashboard and specify the Users and/or User Groups.

On triggering the cache subscription different caches are generated:

Case Cache Type Generated
The base dashboard is not published to the specified User or User Group. None
The base dashboard is published to the specified User, but the User hasn't logged in to Library yet Base dashboard page caches
The base dashboard is published to the specified User, and the User only switches page or resets Dashboard Base dashboard page caches
The base dashboard is published to the specified User, and the User changes the base dashboard Dashboard shortcut page caches

The base dashboard is published to the specified User Group, and the User Group contains User1 and User2. After the Base Dashboard is published to the User Group, User1 has logged in to their Library, but User2 hasn't logged in to their Library. The cache generation for User1 follows Case #3, and the cache generation for User2 follows Case #2.

User 1: Base dashboard page caches or Dashboard shortcut page caches depending on changes made.

User 2: Base dashboard page caches