Changes between Version 24 and Version 25 of MpiKernels

Show
Ignore:
Timestamp:
02/28/12 18:14:08 (13 years ago)
Author:
mmamonski
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MpiKernels

    v24 v25  
    3232} 
    3333}}} 
    34 * A separate Java Virtual Machine is started for every MPI process what increase significally the memory footprint of the whole application. 
     34* A separate Java Virtual Machine is started for every MPI process what increase significally the memory footprint of the whole application 
     35* MPI kernel must be the sole kernel of the particular MUSCLE instance (for this reason, in our example we had to start `plumber` kernel in separate MUSCLE instance) 
    3536* Many MPI implementations exploits low level optimization techniques (like Direct Memory Access) that may cause crash of Java Virtual Machine. 
    3637* Using MPI to start many  Java Virtual Machines, which loads some native dynamic-link library that later calls MPI routines is something that most people rarely do. In case of problems you might not found any help (you have been warned! ;-).