What are the Requirements for Parallel I/O?
The main requirement for this feature is a parallel file system. A command line option is required to activate the feature with Simcenter STAR-CCM+. Further requirements are listed in the following sections.
Parallel File System
A parallel file system is required to get benefits from this feature. Examples of parallel file systems include PanFS from Panasas, Lustre, and the General Parallel File System (GPFS) from IBM. Of parallel file systems, the current capabilities have been tested and tuned for PanFS. The feature should work on other parallel file systems that are supported by the I/O framework of the Message Passing Interface (MPI) standard.
Common Visible Path
A common visible file path on all compute nodes is required for this feature to work correctly. The volume on the parallel file system (where the simulation file is accessed) must:
- be mounted on all compute nodes where the associated Simcenter STAR-CCM+ server processes are being run; and,
- have a common mount point. For example, if a volume is mounted as /foo on some nodes and /fu on other nodes, the simulation file cannot be saved as /foo/bar.sim with parallel I/O since /foo is not visible on some of the nodes.
Simcenter STAR-CCM+ attempts to revert to serial I/O in cases where these requirements are not met, but this is not guaranteed to be successful.
Sufficient Hardware Resources
Even with a parallel file system, sufficient hardware resources must be available to obtain significant performance benefits. For example, with Panasas storage systems, multiple shelves (or blade racks) are required to obtain significant performance improvements relative to serial I/O (especially on a fast network).
Sufficiently large simulations
The benefits of parallel I/O can only be realized for sufficiently large simulation files (typically containing more than 1 million cells). This is because sufficiently large storage blocks are required to effectively stripe across the available file system servers.