clone 895748 -1
retitle -1 Should we switch the standard default MPI to MPICH?
On Mon, 2018-04-16 at 13:21 +0100, Alastair McKinstry wrote:
>
> On 16/04/2018 09:42, Drew Parsons wrote:
> >
> > Thanks Alastair. OpenMPI 3 has just arrived in unstable. Is it
> > still
> > the case that openmpi 3 d
On 16/04/2018 09:42, Drew Parsons wrote:
> On Mon, 2018-04-16 at 08:27 +0100, Alastair McKinstry wrote:
>
> Thanks Alastair. OpenMPI 3 has just arrived in unstable. Is it still
> the case that openmpi 3 does not provide failed image support?
Yes :-(
> Drew
>
--
Alastair McKinstry, , ,
https:/
On Mon, 2018-04-16 at 11:14 +0200, Michael Banck wrote:
>
> One thing I could do is upload a new mpi-testsuite package, which
> tries
> to run (the MPICH testsuite mostly, IIRC) for both MPICH and OpenMPI;
> that might give some input on how good/bad they are on the various
> arches.
That's an ex
Hi,
On Mon, Apr 16, 2018 at 04:42:31PM +0800, Drew Parsons wrote:
> On Mon, 2018-04-16 at 08:27 +0100, Alastair McKinstry wrote:
> > > Now that mpich builds on all arches, it could be a good opportunity
> > > to
> > > review and discuss whether we want to keep openmpi as the default
> > > default
On Mon, 2018-04-16 at 08:27 +0100, Alastair McKinstry wrote:
> > Now that mpich builds on all arches, it could be a good opportunity
> > to
> > review and discuss whether we want to keep openmpi as the default
> > default, or whether we want to switch to mpich.
> >
> I'd favour switching over to
> Now that mpich builds on all arches, it could be a good opportunity to
> review and discuss whether we want to keep openmpi as the default
> default, or whether we want to switch to mpich.
>
> Again historically, openmpi had more bugs than mpich, mainly because it
> was trying to do more things