Memory management

Consolidations run much slower if forced to use paged memory (called swapping). You can use the Task Manager to find out if a consolidation is using paged memory. Compare the numbers for the Commit Charge and Physical Memory on the Performance tab. If Commit Charge is bigger, there is not enough physical memory so consolidations are forced to use paged memory.

If consolidations are using paged memory, you can eliminate swapping by increasing the amount of physical memory on the computer or by reducing memory usage. These are some ways to reduce memory usage:

• Eliminate unnecessary processes that are running during a consolidation. You can find these processes using Task Manager or Performance Monitor. Shut the processes down before running the consolidation.
• Reduce CPM Server memory usage by using several smaller schedules instead of fewer large schedules. The consolidation memory usage is based on the largest of the smaller schedules. When creating smaller schedules, be sure to minimize the number of off-sheet references to retain optimal performance.
• If you run CPM Server and the relational database on the same server, you can reduce database memory usage. These parameters control memory usage for relational databases:
  • MaxMemUsage (Microsoft SQL Server)
  • Shared Pool Size (Oracle)