• Try to anticipate resource usage and avoid resource shortages. Creo Simulate is storage-intensive, so make sure you have ample disk and swap space, and monitor the resource usage periodically. This approach helps prevent an unexpected shortage of resources.

• Resource and performance information is written in the engine log file (the study/study.stt file, where study is the design study name). The engine updates the information in this file for each step of the analysis.

• While your job is running, you can estimate total disk space required by reviewing the information printed in the study/study.pas file immediately after the heading Begin Element Calculations. This information tells you how large the factored global stiffness matrix will be (if you are using the direct solver) and how large the element matrix files will be.

• For jobs using the direct solver, total disk space is approximately the size of the global matrix file plus three times the size of the element matrix file.

• For jobs using the iterative solver, total disk space is approximately the size of the element matrix file plus the global matrix profile for the last pass that used the direct solver (that is, the pass immediately before the first iterative solver pass).

• Some platforms allow you to configure two or more disks together as a striped file system. A striped file system splits disk I/O among several disks in parallel. You may be able to improve I/O performance and reduce elapsed times by directing Creo Simulate working directories to the striped file system.