Memory Pools

To be able to troubleshoot memory bottlenecks it is important to understand ENOVIA Live Collaboration architecture and the various memory pools in use.

Related Topics
Memory Management
Memory Troubleshooting Procedures
Studio Customization Toolkit Origin Tracing

ENOVIA Live Collaboration Server can be configured in two different ways:


  • Two-tier (ENOVIA Live Collaboration Server)—The ENOVIA Live Collaboration kernel lives in its own process as an ENOVIA Live Collaboration Server and has its own memory space. In this case three memory pools are relevant:
    • The C++ memory of the ENOVIA Live Collaboration Server—Used to cache data and evaluate server operations.
    • The Java heap in the ENOVIA Live Collaboration Server—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 ENOVIA Live Collaboration 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 ENOVIA Live Collaboration Server (listed above) are relevant in this configuration.