KB485932: What are the Memory Governing Limits in the MicroStrategy Library for iOS?

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
Strategy Library for iOS has the following 3 memory governing limits when running a dossier, a document or a report:

• Max. Data Slice Size (MB)
• Definition Size (MB)    
• Runtime Size (MB)    

These settings are pre-configured in the app and cannot be changed by user or administrator. The values on both iPad and iPhone are shown below:

Max. Data Slice Size

Each dossier, document or report is cached in multiple files for the Library iOS app. The format of these cache files are either binary_definition or binary_data. Cache type and cache size can be seen from Developer or Workstation Monitors:

When user runs a dossier page, a document or a report, if any of the used cache files exceeds the max data slice size limit, the execution will fail and an error will show:

Definition Size

When user runs a dossier page, a document or a report, one cache file of type binary_definition will be generated. This file will be decompressed after downloaded to the device and the definition size limt controls the maximum file size that the Library iOS app can load into memory after decompression (usually larger than the size of compressed version shown in the Workstation Monitors). If the limit is reached, the execution will fail and the memory governer error will show:

Runtime Size

This controls the total maximum memory usage of the iOS Library app. If the memory consumption is about to exceeds this limit, the memory governer error will show. This error may occur when user opens a dossier page, a document or a report, or does any kind of manipulation afterward, e.g. change filter selections, swipe panel, etc.

Usually these errors are not easy to occur. But if it’s indeed met, review your design and consider following changes:

• Reduce the dataset or cube size by removing unused attributes or unused attribute forms.
• Use workingset report as dataset instead of the original cubes and include only the necessary attributes and metrics.
• Simplify the document design. Split the content into multiple smaller ones and link them together.
• Use dossier instead of document and leverage ToC to split the contents.
  
• Note: When user opens a dossier from Library iOS app, only the caches for the opened page will be loaded. Thus the cache size is smaller than a document with similar design.
• Reduce the panels used in a single page in dossier.
• Reduce the grids or visualizations count on the same screen. The more visualizations shown, the more memory used.
• Apply filter to visualizations or use selectors to control the data amount in each visualization.
• Reduce the row or column counts in a grid.
  
• Note: starting from 11.3.9, the maximum column count allowed in a grid in iOS Library app is upgraded from 50 to 150. So if your grid contains a large amount of columns, the app’s memory usage is higher than in old versions and the memory governor limit may occur in some extreme cases. Try to reduce the column count and check if the grid can be opened successfully.