CAST HIGHLIGHT - Code Reader - Analysis - Performance - Scan takes long time and stops at some file – CAST

While using Highlight Code Reader to scan an application, the scan takes over a day, and seems to stop at some file.

Check in the logs if there is any error when the scan stops.
Check whether memory and/or CPU is maxed out on the machine in which you are analyzing.
If the file count exceeds 10,000
1. It is recommended to split the scan into several separate scans (as mentioned in the getting started guide). Multiple scans (different folders), can be run, then output ZIPs for the same application can be uploaded . Results will be aggregated into a single application result.
  1. Try to 'batch' the analysis and then submit all the CSVs from all batches together.
    For example, if you know that files 1-X are good, you can analyze them all together. Then you can analyze files X+1 to X+Y and analyze them together and then analyze X+Y to X+Z together.
    
    To avoid the algebraic reference, you can analyze for example:
    
    Files 1-5000
    Files 5001-10000
    Files 10001-15000
    Files 15001-20000
    
    all separately (and possibly even in parallel if your machine has enough CPU and memory) and then put together all the resulting CSVs for the application.
Select source folders on your local machine, though the Code Reader supports source discovery through network paths, if your system permissions allow to do so. You can manually separate the code first or you can maybe split up the source code folders (so choose folders A-L and then M-Z or something like that).
Try using the latest version of the Highlight CLI/Code Reader and possibly the CLI by itself.

39886

CAST HIGHLIGHT - Code Reader - Analysis - Performance - Scan takes long time and stops at some file