To get maximum benefit from running Crystal Ball in Extreme speed, you should be aware of several issues in the models that could potentially cause simulations to run more slowly than expected.
When you first start a simulation in Extreme speed, the model is analyzed and converted into a special form for high-speed processing. This form involves the use of a technique called vectorization to process batches of formula results together for maximum efficiency. Certain functions and formula constructs in the model can interfere with this vectorization process. Some of the more common cases are discussed in the following sections:
If one or more cases are detected, Crystal Ball Decision Optimizer displays the message "non-vectored" on the Microsoft Excel status bar while the simulation is running. Also, additional information is usually written to the Crystal Ball log file, which can be found with the suffix CB Log and extension .txt in:
C:\Documents and Settings\username\Application Data\Oracle\ Crystal Ball\11.0\Logs\CB Log_x.txt
If you have a very large number of trials, the virtual memory feature of Microsoft Windows is activated. This can slow down processing. Too, if you have large numbers of forecasts and assumptions, managing these large arrays of values can take extra time. If you think array management could be an issue, try unchecking Store Assumption Values For Sensitivity Analysis on the Options tab of the Run Preferences dialog. |