When modeling systems with low-probability, high-consequence outcomes it is sometimes necessary to run a large number of realizations. When a realization A single model run within a Monte Carlo simulation. It represents one possible path the system could follow through time. can be run quickly the amount of time spent transferring information to Client Also referred to as a Client process. A GoldSim executable running on a client machine that can be used to carry out distributed processing of a Monte Carlo simulation using the Distributed Processing Module. processes for each realization individually can negate the performance benefits of distributed processing. As a result, GoldSim has an option to assign a block of realizations to a Client process. This option is accessed by pressing the Additional Client Settings button:
When you do so, the following dialog is displayed:
A block of realizations can be assigned to a Client process by using the Realizations to run per client transaction.
By default the value is 1 (indicating a single realization will be assigned each time). The value can be increased to any number that is desired (e.g. specifying 5 means that the first Client transaction will assign realizations 1-5, the second 6-10 and so on).
- Aborting a Distributed Processing Simulation
- Activating, Deactivating and Terminating Client Processes During a Simulation
- Assigning Multiple Realizations to Each Client Transaction
- Assigning Realizations to Multiple Clients at the End of the Simulation
- Distributed Processing Auxiliary Files and Working Folders
- Distributed Processing Log Files
- Recovering a Simulation When the Controller Process Fails