CMS Snapshot Analysis - Run Analyzer - Performance issue

This page will help you to troubleshoot the performance problems, you may face while running the analysis. Performance issue during analysis means one of the following:

• the analysis is taking longer than expected to finish.
  
• the analysis is stuck and never ends

For more information, refer to:

Official documentation :

• Official 8.3 Documentation - Run and validate the analysis
  

Information Guides > Information Guides by CAST AIP Component > CMS Snapshot Analysis

Error Free Logs - CMS Snapshot Analysis - Run Analysis for Technology - Error Free Logs - CAST AIP 83

1. Package and Deliver the application.
2. Set as current version.
3. Run the analysis (Application level or Analysis Unit Level).
4. Analysis is stuck or is taking longer then expected to finish.

Perform the following steps:

1. Open the analysis log in a text editor(like NotePad++) and search for the keyword "Execution duration".
   1. If the above search returns a result, then the analysis has finished. In this case you will have to identify the analysis step(s) responsible for the performance issue
      1. Observe the delta in the timestamps for each information message in the analysis log. For the following example:
         
         The delta for the 2 parsing messages is 1m1s
      2. Compare the above with the timestamps of reference for the particular technology, this can be found under CMS Snapshot Analysis - Run Analysis for Technology - Error Free Logs - CAST AIP 83
      3. Identify the step(s) responsible for the performance issue. Note that some steps are specific to the analyzed technology.
   2. If there is no result in the analysis log, then the analysis is stuck and the performance issue is happening during the action logged in, found in the last information message or the next expected action since the analyzer may not have logged the last current action.

      1. Identify the step for the analyzed technology in analysis log reference which can be found in  CMS Snapshot Analysis - Run Analysis for Technology - Error Free Logs - CAST AIP 83
         Example : For J2EE analysis, if the last line is:

         2016-11-04 10:01:36.218 Information MODULMSG ; Job execution Ending External Link processing

         Then the issue can happen during Resolving External Links OR during the next step, aka Saving Step. You have to consider both situations.
         
         

2. According to the identified steps:

   1. If the issue occurs before the "About to run <Execution Unit>" information message:

      
      

      then it is happening during the analysis configuration. Navigate to CMS Snapshot Analysis - Run Analyzer - Performance issue - Configuration Step

   2. If the issue occurs after the "About to run <Execution Unit>" information message:

      

      then it is happening during the beginning of the analysis. Navigate to CMS Snapshot Analysis - Run Analyzer - Performance issue - Beginning of analysis

   3. If the issue occurs during the parsing/processing/visiting information message:

      

      then it is happening during the analysis and parsing of the source code. Navigate to CMS Snapshot Analysis - Run Analyzer - Performance issue - Analyze Source code step

   4. If the issue is happening after the "Comparing objects on server . . ." information message:

      
      then it is happening during the saving step of the analysis. Navigate to CMS Snapshot Analysis - Run Analyzer - Performance issue - Saving Step

3. If you do not find the information you are looking for or solution for your problem, in this page, contact CAST Technical Support with Relevant Input
   

Relevant Input

1. Run analysis by Enabling the memory traces .
2. Provide Sherlock (CAST Support Tool (CST) - alias Sherlock) with options : Export Management+Local Databases, Export Logs, Export configuration files, Export source code. 
   

.