Memory Pools

To be able to troubleshoot memory bottlenecks, it is important to understand 3DSpace architecture and the various memory pools it uses.

See Also
Memory Management
Memory Troubleshooting Procedures
Studio Customization Toolkit Origin Tracing

3DSpace Service can be configured in two different ways:

  • Two-tier (3DSpace Service)—The 3DSpace kernel lives in its own process as an 3DSpace Service and has its own memory space. In this case three memory pools are relevant:
    • The C++ memory of the 3DSpace Service—Used to cache data and evaluate server operations.
    • The Java heap in the 3DSpace Service—Used to temporarily store data for requests, until the request is completed.
    • The Java heap in the application server—Used to store all Java objects of the application, like sessions, beans, properties and temporary objects.
  • Single tier (RIP)—The 3DSpace kernel is part of the application server and shares the same address space. The memory pools in C++ memory and the Java heap in the 3DSpace Service (listed above) are relevant in this configuration.