RPI module (vs. other RPI modules)?
Although the lamd RPI module is typically slower than other RPI modules (because MPI messages generally must take two extra hops before ending up at their destination), the lamd RPI has the following advantages over its peer RPI modules: • Third party applications such as XMPI can monitor message passing, and create reports on patterns and behavior of your MPI program. • The LAM daemon can exhibit true asynchronous message passing behavior. That is, the LAM daemon is effectively a separate thread of execution, and can therefore make progress on message passing even while the MPI application is not in an MPI function call. Since LAM/MPI is currently a single-threaded MPI implementation, most other RPI modules will only make progress on message passing while in MPI function calls. Therefore, MPI applications that can use latency-hiding techniques can actually achieve good performance from the lamd RPI module, even though the latency is higher than other RPI modules. This strategy has bee
Related Questions
- Can the user have a mix of real IO modules and simulated IO with MiMiC and the Virtual IO Module on the same controller?
- Can the user have a mix of real IO modules and simulated IO with MiMiC and the Virtual IO Module on the same controller?
- Is Ryanair Module linked to other Pack Alan Rogers modules and Ctoutvert marketing products?
- Is Ryanair Module linked to other Pack Alan Rogers modules and Ctoutvert marketing products?
- How do I license a High Availability Module for two VPN/FireWall Modules?
- RPI module (vs. other RPI modules)?
