Applies to:

Hyperion Planning - Version: 4.1.0.0.00 to 11.1.1.3.00 - Release: 4.1 to 11.1
Information in this document applies to any platform.

Goal

We are receiving periodic "Out Of Memory" errors in the Planning web application logs. What can we do to allocate more memory or otherwise improve the performance of our Planning applications?

Solution

There are three things you can do to improve the performance of the Planning application.

I. Increase the Java heap size

You can increase the heap to a maximum of 1Gb (1024Mb). If you have the available RAM to dedicate to Planning, it is recommended to increase both the minimum (Xms) and maximum (Xmx) heap size to 1024Mb. Inceasing the minimum heap size will help because it lowers the overhead needed to manage garbage collection in a dynamically expanding heap. Do not exceed 1024Mb or you may see performance actually decrease.

The step by step procedure for modifying the Java heap size varies from one web application server to another. Contact your web application administrator for assistance.

II. Turn off process management for Version and Scenario members for which it is not needed

By default, new Scenario and Version members are enabled for process management. Each Entity-Scenario-Version combination (each Planning unit) costs resources because Planning must check who currently owns the Planning unit and check the security settings. If you have many Scenarios and Versions the number of combinations increases rapidly.

Decide what Versions and Scenarios need to be available for process management, and then disable the others. If you are not using process management at all then you can disable process management support for all Version and Scenario members. To disable process management support, edit a member of the Scenario or Version dimension. In the member properties, uncheck the "Enable for process management" checkbox. Repeat for each member you want to disable process management for. When finished, restart the Planning service.

III. Optimize the design of web forms

Large web forms impose by far the heaviest load on the Planning JVM. Optimizing the design of forms can make a big difference to how fast a form. opens and how many users can open it concurrently.

Web form. design is a complex area. Please see Note 779502.1 for more information on best practice for web form. design.

Although the three sections above explain where the main performance gains can be made, this does not mean that all Planning performance problems can be traced back to one of these three. For example, poorly structured user and group provisioning (many levels of nested groups, or systematically provisioning at the user level rather than at group level) can cause slow logins, as can connections to large external directories that have not been optimized with filters in Shared Services. Similarly, systematically assigning access privileges to Business Rules in EAS at the user level or using many levels of nested groups can cause performance problems in Planning if you are using Business Rules set to "Run on save" on web forms.

ITPub博客

Improve The Performance Of Hyperion Planning

Applies to:

Goal

Solution

I. Increase the Java heap size

II. Turn off process management for Version and Scenario members for which it is not needed

III. Optimize the design of web forms

最新文章