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

KB484753: The maximum memory allocation pool for the Modeling service is not configured correctly on the Strategy Cloud Platform


Community Admin

Placeholder •


This article discusses a known defect (DE183559) in which the default value of the maximum memory allocation pool for the Modeling service is not configured correctly in a Cloud deployed environment with 64GB or larger RAM.

Description

The default value for the Modeling service’s maximum memory pool size is set during the installation of the Modeling service. The value is set based on the machine’s RAM size. For example, 1GB for a machine with RAM of 8-32GB or less, 2GB for a machine with RAM of 64-128GB.
For details, please refer to see Modeling Service Configuration Properties.
However, in a Strategy Cloud Platform environment, the default setting is always 1GB, even when the user configures the machine with 64GB or more memory.

Steps to reproduce

  1. Deploy a Strategy Cloud environment with 64 GB or more RAM.
  2. Locate modelservice.ini in /opt/mstr/Strategy/install/ModelingService/bin.
  3. Look at the MODELSERVICE_JAVA_MAX_MEMORY property. For a machine with 64GB of RAM, it is set as 1GB instead of the expected value of 2GB.

Why is this happening?

When a Strategy Cloud Platform environment is deployed, first it creates a new environment based on the pre-created template. Then it adjusts the machine configurations (e.g., RAM size) according to the user’s selection. As the template machine is with RAM of 30.5GB, the maximum memory pool size for Modeling service is configured as 1GB.

Workaround

The workaround for this defect is to manually change the property MODELSERVICE_JAVA_MAX_MEMORY in modelservice.ini.

  • Locate modelservice.ini in /opt/mstr/Strategy/install/ModelingService/bin.
  • Change the MODELSERVICE_JAVA_MAX_MEMORY property to the desired size. For example, if your machine has 512GB memory, change it to 3GB.

ka0PW0000005i3dYAA_0EM4W000001K1BA.jpeg
  • Restart the Modeling service.


Comment

0 comments

Details

Knowledge Article

Published:

December 10, 2020

Last Updated:

May 15, 2025