Page tree
Skip to end of metadata
Go to start of metadata
Purpose

This page will help you to solve problems related to Performance issues that occur during the configuration steps of the analysis.

*Observed in CAST AIP


Release

Yes/No

8.3.x(tick)
8.2.x(tick)
8.1.x(tick)
8.0.x (tick)
7.3.x (tick)
*Observed on RDBMS

RDBMS

Yes/No

Oracle Server (tick)
Microsoft SQL Server (tick)
CSS2 (tick)
CSS3(tick)
Action Plan

Perform the following steps::

  1. Check if the LISA folder is on the analysis server or a remote server. LISA folder is used by the analyzers as a working folder, to either read files or create/generate files useful for analysis.
    1. If the LISA folder is on a remote server, verify the local network speed by copying a large file (1GB) from the remote location to the analysis server and compare the speed to your theoretical LAN speed. As a solution you can set the  LISA folder as a local folder or improve the network infrastructure
  2. Check the Analysis Server Performance. Open Windows Task Manager:
    1. Check the memory consumption for the CAST analyses processes.  These can be anarun, dotnetcmd, and jeecmd, depending on what is being run. For example if you are running an analysis with a system memory of 8 GB and if one of the CAST analyses processes has a memory consumption is 4 GB, then this can be the reason for the performance issue. Check Deployment - sizing to find out the hardware specifications required for each scenario.
    2. Check if CPU usage has reached 100%. If yes, check if other processes are running in parallel and consuming resources. In that case stop the other processes.
  3. Optimize analysis configuration with regards to the referenced project libraries.
    1. For JEE: 
      1. The jar files defined in Technology or Analysis Unit options in Archive Folder options are first extracted in the LISA Folder. For a large number of JAR files this can lead to performance issues. Replace the Archive Folder, by selecting explicitly the.jar files (as Archive Files) that are used by the application or analysis unit.
    2. For Mainframe:
      1. Check if the length of source code files is longer then column 72. The analysis can get stuck in 'Validation successful' message or during parsing a file when the column length > 72
        1. Open CAST_MS in Technology Options for Mainframe and select 'Source code can be placed beyond column 72' option
        2. Rerun analysis and verify if issue is solved
    3. If you do not find the information you are looking for or solution for your problem, on this page, contact CAST Technical Support with Relevant Input
Notes


Related Pages


  • No labels