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. Increasing 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 notneeded:
By default, new Scenario and Version
members are enabled for process
management.Each Entity-Scenario-Version combination (each Planning unit) costs resources becausePlanning
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, do a database refresh using the Administration>Manage
Database page and 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