Hi Lars,
First off, I think Jeff makes some very good points.
If you still think your applications will benefit from yielding
instead of hogging the cpu,
you should probably try to use the parameter "mpi_show_mca_params".
This will give you a list of the mca parameters at runtime. This way
Sorry for the delays in replying.
The central problem is that Open MPI is much more aggressive about its
message passing progress than LAM is -- it simply wasn't designed to
share well as a mechanism to get as high performance as possible.
mpi_yield_when_idle is most helpful only for certai
On Fri, Apr 4, 2008 at 4:30 PM, Lars Andersson wrote:
> Hi,
>
> I'm just in the progress of moving our application from LAM/MPI to
> OpenMPI, mainly because OpenMPI makes it easier for a user to run
> multiple jobs(MPI universa) simultaneously. This is useful if a user
> wants to run smaller e
Hi,
I'm just in the progress of moving our application from LAM/MPI to
OpenMPI, mainly because OpenMPI makes it easier for a user to run
multiple jobs(MPI universa) simultaneously. This is useful if a user
wants to run smaller experiments without disturbing a large experiment
running in the backgr