EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

Workstation Feature: Cache Management


Yifan Liu

Product Owner • Strategy


Viewing and Managing Application-level caching options in Workstation for dossiers and reports.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
Best Practices
Cache Management
As an administrative tool, Workstation should provide the ability to manage cache creation and governance on an Application level. Caching is important for performance, and Workstation should enable administrators to set cache options and sizes for each of their Applications. Previously, Developer provided this functionality with various options, many of which were determined to not be primary to users (for example, selecting the formats for the caching). The redesigned interface in Workstation provides straightforward options for cache settings.
 
Administrators can enable or disable caching overall, as well as specify cache sizes for the two different caches: the report cache, and the document/dossiers cache. In addition, administrators can enable caching of Library dossiers (dossiers that belong to the Application, that are in any users' Library) and bookmarks (an 11.0 feature that allows you to bookmark dossiers), as well as bookmark caching for subscriptions. 
Value
 
Disabling caching for an Application
The user is experiencing overall performance issues in programs running on the server that does caching for a particular Application. The caching is using too much of the machine's resources, and the particular Application isn't heavily used by many users, executing many different dossiers. Therefore, the administrator would like to disable all report and dossier caching for this particular Application. 
Increasing the cache size
The user wants improved performance of execution in a particular Application. This Application is more heavily used by more users, with frequent dossier executions. Therefore, the administrator would like to increase the cache size for dossiers up to 10,000 MB, for a particular Application.
Enable Bookmark Subscription caching
There are performance issues for subscriptions to dossiers that originate in a particular Application. It seems that these dossiers have bookmarks in them. To improve this performance, the administrator would like to enable bookmark caching for subscriptions in this particular Application.
 
Architecture
Workstation provides the option to disable or enable caching completely, as well as specify cache sizes for the two different caches: the report cache, and the document/dossiers cache. In addition, administrators can enable caching of bookmarks, as well as bookmark caching for subscriptions. By default, all of these options are enabled. 
These options are stored as properties of a particular application. They are stored independently in the server, though they are presented in a hierarchal structure in Workstation. Workstation enforces this hierarchical structure. For example, in the Enable Bookmark Subscription caching use case above, the user must first have selected Enable caching as well as Enable Library and bookmark caching to complete the Workflow. 
Requirements
 
Here are some of the requirements that must be met in order to successfully see the telemetry.

  • The current Environment must be version 11.0 or later.
    • Need help with upgrading? Learn more.
  • The user trying to make the changes must have been granted the “Configure Governing” privilege for the Application.
    • This can be done through Developer. Learn more.
  • The user must also have Write permissions for the Application. 
    • The ACL for the user can be edited by an Administrator. Learn more.

Action Steps

  1. Navigate to the Applications tab in Workstation
  2. Right mouse click the Application and select “Get Info”
  3. Select the Cache Management tab*
  4. Click the “Save” button to save any changes made
     

*If you do not see the Cache Management tab, this is because you do not have the "Configure Governing" privilege for this Application
 
Using Developer and Workstation?

ka0PW0000001JWPYA2_0EM44000000RU7b.png

 

  1. GREEN: The options highlighted in green are directly mapped to each other between Developer and Workstation. That is, if "Enable report server caching" is selected in Developer, "Enable Caching" will be selected in Workstation, and vice versa. Selecting or deselecting these options in either app does not affect the state of the other options.
  2. RED: The options highlighted in red are directly mapped to each other between Developer and Workstation. In Developer, this option is found under Caching → Result Caches → Storage: Datasets - Maximum RAM usage (MBytes). 
  3. BLUE: The options highlighted in blue are directly mapped to each other between Developer and Workstation. In Developer, this option is found under Caching → Result Caches → Storage: Formatted Documents - Maximum RAM usage (MBytes). 
  4. All other options seen in either Developer or Workstation are independent of one another. For example, the options in Workstation to "Enable Library and bookmark caching" and "Enable bookmark subscription caching" are not affected by (nor do they themselves affect) any options in Developer.

Boundary Conditions/ Edge Cases

  • Maximum Values - for document/dosser and report caches, the maximum cache size is 1048576 MB (1 TB). The input box will not allow numbers larger than this. 
  • Permissions & Privileges
    • If the user does not see the Cache Management tab, it is because they do not have the Configure Governing privilege. See Requirements
    • If the user cannot save their changes, it may be due to a lack of write permission on the Application. See Requirements
  • Developer & Workstation
    • Since the settings are not directly mapped, if any user is also trying to view or change these settings in Developer, please see Using Developer and Workstation?


Comment

0 comments

Details

Knowledge Article

Published:

December 10, 2018

Last Updated:

March 21, 2024