CAST Imaging is a CPU and RAM intensive application, and this is especially true if you are importing large and complex applications. The following page lists some configuration changes that may help improve performance of CAST Imaging while importing and investigating applications.
Optimize RAM allocated to CAST Imaging
By default Neo4j is set to use the following RAM:
|CAST Imaging ≥ 2.5.0||8GB of RAM memory (initial and maximum)|
|CAST Imaging ≤ 2.4.x||3GB of RAM memory (initial and maximum)|
If you are facing performance issues, it is possible to increase the RAM allocated to CAST Imaging - you can also run a memory test to provide you with suggested RAM allocation based on the total amount of RAM available on the host. See Optimize Neo4j memory allocation.
Optimize Neo4j disk usage - transaction log retention
By default Neo4j is set to retain transaction logs (used for database backup operations) for 7 days, however, transaction logs can grow significantly in size, increasing the overall size of the graph.db file and therefore reduce overall performance. If you are facing disk space/performance issues due to the size of the graph.db file, you can change the transaction log retention time. See Optimize Neo4j disk usage - transaction log retention.
See the options Node Limit / Edge Limit in Configuring display preferences to set the rendering threshold for nodes/edges.
Import application performance
Import batch size
Some applications can be very large and therefore can take a significant amount of time to import into CAST Imaging. During the application data import process (see Export and import the Application data), CAST Imaging is configured to import data in a batch of 1000 rows and then perform a commit. If you have allocated additional memory to Neo4j (see Optimize Neo4j memory allocation) it is possible to increase the default import batch size so that data commits are performed less, therefore increasing overall import performance. See Configuring import batch size.
Export application performance
PostgreSQL on Microsoft Windows
If you are attempting to export from a PostgreSQL instance installed on Microsoft Windows (i.e. CAST Storage Service) and your application is very large, you may find that the export process fails with the error which is caused by a timeout. To resolve this issue, see the section "[WinError 10054] An existing connection was forcibly closed by the remote host" in Automation tool export and import process and Export the CSV data.