Using Parallel I/O

For systems that support it, simulation files can be saved and restored using parallel input/output (I/O).

With serial I/O (the default behavior), a single Simcenter STAR-CCM+ server process performs all the data input and output on behalf of all server processes, scattering and gathering data as needed. This data flow creates a serial I/O bottleneck that can limit save and restore performance. With parallel I/O activated, multiple Simcenter STAR-CCM+ server processes perform the I/O operations concurrently using the parallel file system. This option mitigates the serial I/O bottleneck, and can potentially reduce the time it takes to save and restore data.

To activate parallel I/O, you require a parallel file system. Using the feature on a locally mounted file system or network file system (NFS) usually provides no performance benefit, and can actually reduce performance. NFS is not a parallel file system.

The format of simulation (.sim) files that are saved with parallel I/O activated is the same as the format of simulation files that are saved using default serial I/O. A simulation file that is saved using parallel I/O can be read using serial I/O. Similarly, a simulation file that is saved using serial I/O can be read using parallel I/O.

Backward Compatibility

You can restore all old simulation files using parallel I/O. To obtain the full performance benefit of parallel I/O on restore, the simulation file must have been saved using Simcenter STAR-CCM+ version 6.06 or higher. Although the simulation file format for serial and parallel I/O are the same, the format was revised for version 6.06 to improve its application to parallel I/O.

Limitations

Current limitations are:

  • Linux only. Currently, parallel I/O is only available on Linux platforms.
  • Simulation files only. Currently, the capability is only available for saving and restoring .sim files.