Microstrategy Caches explained

Microstrategy Caches

Improving Response Time: Caching

A cache is a result set that is stored on a system to improve response time in future requests. With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database.

To delete all object caches for a project

1

In Developer, log into a project. You must log in with a user account that has administrative privileges.

2

From the Administration menu, point to Projects, and then select Project Configuration. The Project Configuration Editor opens.

3

Expand Caching, expand Auxiliary Caches, then select Objects.

To delete all configuration object caches for a server

1

Log in to the project source.

2

From the Administration menu in Developer, point to Server, and then select Purge Server Object Caches.

4

Click Purge Now.

To purge web cache follow the steps in the link below:

https://microstrategyanalytics.blogspot.com/2018/12/purge-web-caches-in-microstrategy-web.html

To purge various other caches go the MSTR link below: 

https://community.microstrategy.com/s/article/KB42534-How-to-clear-the-various-caches-interacting-with?language=en_US

Improving Response Time: Caching

A cache is a result set that is stored on a system to improve response time in future requests. With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database.

Intelligence Server supports the following types of caches:

• Page caches: When a user views a published dossier the Intelligence Server generates one cache per page, so that the cache can be hit when the user switches between pages.

• Result caches: Report and document results that have already been calculated and processed, that are stored on the Intelligence Server machine so they can be retrieved more quickly than re-executing the request against the data warehouse. Intelligent Cubes can function in a similar fashion to result caches: they allow you to store data from the data warehouse in Intelligence Server memory, rather than in the database. Intelligent Cubes are part of the OLAP Services add-on to Intelligence Server. For detailed information about Intelligent Cubes.

• The History List is a way of saving report results on a per-user basis. 

• Element caches: Most-recently used lookup table elements that are stored in memory on the Intelligence Server or Developer machines so they can be retrieved more quickly. 

• Object caches: Most-recently used metadata objects that are stored in memory on the Intelligence Server and Developer machines so they can be retrieved more quickly. 

You specify settings for all cache types except Page caches and History List under Caching in the Project Configuration Editor. Page cache settings are configured via Application Properties > Dossier Cache Management in MicroStrategy Workstation. History List settings are specified in the Intelligence Server Configuration Editor.
Result, element, and object caches are created and stored for individual projects; they are not shared across projects. History Lists are created and stored for individual users.
To make changes to cache settings, you must have the Administer Caches privilege. In addition, changes to cache settings do not take effect until you stop and restart Intelligence Server.