Parallel
Configure parallel processing.
Syntax
Parallel <AppOrScenPath> {ParallelOption}
Related commands
Description
The <AppOrScenPath> can be either the Application path or the Scenario path. The following table describes the available options.
{ParallelOption} | Description | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Configuration ParallelType {Local | Cluster} [{Parameters}] | If Local is entered then the optional {Parameters} can be:
If Cluster is entered then the optional {Parameters} can be:
| ||||||||||||||||||||||||||||||||
AutomaticallyComputeInParallel [{Coverage | Deck Access | ChainAccess | Volumetrics}] {On | Off} | The options in brackets [] are optional additional options for parallel computing. You should only use one argument (i.e. Parallel / AutomaticallyComputeInParallel Coverage On. The command NACKS if you use Parallel / AutomaticallyComputeInParallel Coverage DeckAccess On.) When On, always use parallel mode when computing coverage, deck access, chains or volumetric, either explicitly or as a result of changes made to other objects in the scenario. | ||||||||||||||||||||||||||||||||
ComputeAllFiguresOfMeritInParallelWithCoverage {On | Off} | By default only certain types of figures of merit (those usually expensive to compute) are computed in parallel. This forces all the figures of merit to compute in parallel, independently of their type. In those cases this might be less efficient than not computing in parallel, due to the overhead involved in starting up a parallel computation. | ||||||||||||||||||||||||||||||||
HostLoggingLevel {All | Info | Warning | Error} | Sets the logging level used by the hosts. | ||||||||||||||||||||||||||||||||
ScenarioOptions [{parameters}] | Sets the values for the designated parameters at the scenario level.
The UseTaskEstimatedMemoryUsage argument specifies whether or not the task’s estimated memory usage will be compared to the agent’s estimated memory budget when scheduling parallel tasks. The TaskEstimatedMemoryUsage option specifies the estimated amount of memory the task is believed to use, measured in MB. The options for [{parameters}]:
UseTaskEstimatedMemoryUsage turns On or Off the use of an EstimatedMemoryUsage for each task. TaskEstimatedMemoryUsage sets the value of the EstimatedMemoryUsage for each task. | ||||||||||||||||||||||||||||||||
ShutdownLocalWorkers | Forces all local workers to shutdown. Only available when using the Local parallel type. | ||||||||||||||||||||||||||||||||
ShutdownLocalWorkersOnJobCompletion {On | Off} | When On, local workers shut down after completing their work (instead of staying in memory to allow better startup time for the next computation). | ||||||||||||||||||||||||||||||||
ValidateScenario {On | Off} | When On, scenarios are automatically validated prior to starting a parallel computation. | ||||||||||||||||||||||||||||||||
SaveInBinary {True | False} | Enables or disables whether the scenario used for the computation is saved in a binary format that is more efficient for loading in parallel processes. |
Examples
To set the UseTaskEstimatedMemoryUsage to true:
To indicate that computing should use parallel computation:
To set the parallel type to Cluster:
To set the parallel type to Cluster:
Return message
Group membership
This command belongs to the following group(s):
Version
12