Dear all,
thanks a lot. So basically the idea is that MPI is more useful when a lot
of communication occurs in the calibrator. On the other hand, the jobs
scheduler is more appropriate when there are no or few communications.
Is my final statement correct?
Thanks a lot
Diego
On Thu, 30 Aug 2
Dear all,
thanks a lot.
Diego
On Wed, 29 Aug 2018 at 00:13, Nathan Hjelm via users <
users@lists.open-mpi.org> wrote:
>
> Yup. That is the case for all composed datatype which is what the tuple
> types are. Predefined composed datatypes.
>
> -Nathan
>
> On Aug 28, 2018, at 02:35 PM, "Jeff Squy
Diego,
what you wont to do is parametric studies. There are specific software available
to do this efficiently (ie reducing the number of runs). Software can then rely
in a job scheduler (PBS, SLURM...) which can launch many parallel mpi
applications at the same time depending on the results o
I am compiling openmpi-3.1.2 on CentOS 7 with GCC 7.3 installed in /opt/GCC7. My
setup is "debug" as I had some trouble with MPI lib.
When I run a ldd command on libmpi_usempi.so it shows that it load
libgfortran.so.4 (from GCC 7.3) but also libgfortran.so.3 (from system GCC
4.8.5) and there is
