Manage Java Heap Size
- malaya.panigrahi (Unlicensed)
- Suhas Deshpande
For (very) huge models, Creator Workbench starts to run out of memory, especially when other processes (including OS related) are already consuming memory. This may cause other errors to popup from the Workbench and the log files.
One way to increase the memory available for Workbench is to increase “Java Heap” size, that Creator’s Eclipse Workbench uses.
Recommendation: For standard sized models, recommendations are available in Conformiq Manual within Creator for various machine configurations. However, for (very) huge models, the max setting for model of this size can be greater than given but less than the available RAM in the machine. |
Please note, increasing heap size only pushes the “out of memory” issue to a later point. Issue can still occur if model size increases to (very) large and there are other applications/processes (not related to Creator) consuming memory.
Also, TC generation and other “computation server” processes (“qdcnodes”) are outside of Eclipse, and therefore, do not fall within “Java heap”. Therefore, increasing heap-size does not have any “positive” effect on TC generation performance. On the other hand, there might be even less memory for the computation server to use if running on the same machine, so then the test generation phase might run out of memory.
Recommendation: If, even after increasing the heap size, there is frequent recurrence of “out of memory” issue, please look to handle the model size as recommended in other sections of the deployment guidelines. |
Related content
Copyright © 2023 Conformiq and its subsidiaries. All rights reserved.