Main Content

-max-processes

Specify maximum number of processors for analysis

Syntax

-max-processes num

Description

-max-processes num specifies the maximum number of processes that you want the analysis to use. On a multicore system, the software parallelizes the analysis and creates the specified number of processes to speed up the analysis. The valid range of num is 1 to 128.

Unless you specify this option, a Code Prover verification uses up to four processes. If you have fewer than four processes, the verification uses the maximum available number. To increase or restrict the number of processes, use this option.

Unless you specify this option, a Bug Finder analysis uses the maximum number of available processes. Use this option to restrict the number of processes used.

To use this option effectively, determine the number of processors available for use. If the number of processes you create is greater than the number of processors available, the analysis does not benefit from the parallelization. Check the system information in your operating system.

Note that when you start a verification, a message states the number of logical processors detected on your system. However, the analysis is parallelized to the physical processor cores on a machine. Multithreading implementations such as hyper-threading is not taken into account.

If you are running an analysis from the user interface (Polyspace® desktop products only), on the Configuration pane, you can enter this option in the Other field. See Other.

Examples

Disable parallel processing during the analysis:

  • Bug Finder:

    polyspace-bug-finder -max-processes 1
  • Code Prover:

    polyspace-code-prover -max-processes 1
  • Bug Finder Server:

    polyspace-bug-finder-server -max-processes 1
  • Code Prover Server:

    polyspace-code-prover-server -max-processes 1

Tips

You must have at least 4 GB of RAM per process for analysis. For instance, if your machine has 16 GB of RAM, do not use this option to specify more than four processes.

This option is not useful in a Polyspace as You Code analysis.