Hello Lucas,
Le mar. 13 sept. 2022 à 14:23, Lucas Chaloyard via users <
users@lists.open-mpi.org> a écrit :
> Hello,
>
> I'm working as a research intern in a lab where we're studying
> virtualization.
> And I've been working with several benchmarks using OpenMPI 4.1.0 (ASKAP,
> GPAW and Incompac
starts; it's nothing that the
application itself needs to do.
--
Jeff Squyres
jsquy...@cisco.com
From: users on behalf of Gilles Gouaillardet
via users
Sent: Tuesday, September 13, 2022 9:07 AM
To: Open MPI Users
Cc: Gilles Gouaillardet
Subject: Re: [OMPI
that the
application itself needs to do.
--
Jeff Squyres
jsquy...@cisco.com
From: users on behalf of Gilles Gouaillardet
via users
Sent: Tuesday, September 13, 2022 9:07 AM
To: Open MPI Users
Cc: Gilles Gouaillardet
Subject: Re: [OMPI users] Hardware topology inf
Lucas,
the number of MPI tasks started by mpirun is either
- explicitly passed via the command line (e.g. mpirun -np 2306 ...)
- equals to the number of available slots, and this value is either
a) retrieved from the resource manager (such as a SLURM allocation)
b) explicitly set in a
Hello,
I'm working as a research intern in a lab where we're studying virtualization.
And I've been working with several benchmarks using OpenMPI 4.1.0 (ASKAP, GPAW
and Incompact3d from Phrononix Test suite).
To briefly explain my experiments, I'm running those benchmarks on several
virtual