From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 27850@debbugs.gnu.org
Subject: [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple
Date: Tue, 01 Aug 2017 21:10:23 +0100 [thread overview]
Message-ID: <874ltr9hhs.fsf@i-ulialbion.it.manchester.ac.uk> (raw)
In-Reply-To: <87bmnzxk50.fsf@inria.fr> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Tue, 1 Aug 2017 19:39:23 +0200")
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>> Maybe, but what about the non-ABI compatibility I expect there is? (I
>> don't know whether there's still any penalty from thread-multiple
>> anyhow; I guess not, as I see it's not the default.)
>
> I propose this because you had written that the “performance penalty for
> thread-multiple is supposed to be mitigated in the most recent openmpi.”
> If it’s not, then fine.
I don't know the value of "mitigated". I could ask or, better, measure
when I get back from holiday (at least micro-benchmarks over
Infiniband).
>> If anyone's using it seriously, I'd have thought effort would be better
>> spent on support for SLURM (as it's in Guix) and supporting
>> high-performance fabrics (which I started on).
>
> You already mentioned openfabrics a couple of times I think. Mentioning
> it more won’t turn it into an actual package. :-) It’s on my to-do
> list, I guess it’s on yours too, so we’ll get there.
Sure. It's only what seems important. I'll post what I've got, but if
someone else is doing it, fine, and I won't duplicate effort.
> What do you have in mind for SLURM?
There's integration with SLURM (--with-slurm), PBS/Torque, and LSF (or,
I guess, Open Lava in the free world). I don't know much about them,
but they build MCA modules. Unlike the gridengine support, they link
against libraries for the resource managers, so you want them to be
add-ons which are only installed when required (not like the Fedora
packaging).
> As for “using it seriously”, I think this is a needlessly aggressive way
> to express your frustration.
I'm sorry I'm mis-communicating trans-Manche, at least. It wasn't meant
like that at all and I'll try to be more careful. Please assume I'm a
friendly hacker, even if I have strong opinions, which I hope I can
justify!
> People *are* using Guix “seriously” in HPC
I meant openmpi, not Guix generally. "Seriously" meant applications
which are communication-intensive (like the latency-sensitive DFT
applications).
> already, but (1) different application domains emphasize different
> aspects of “HPC”, and (2) there’s on-going work to improve Guix for HPC
> and your feedback is invaluable here.
I hope I can give useful feedback, and any criticism is meant
constructively. However, I'm not representative of UK HPC people --
happier to use functional Scheme than Python, and believing in packaging
for a start!
Happy hacking.
next prev parent reply other threads:[~2017-08-01 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 15:01 [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple Dave Love
2017-07-31 15:16 ` Ludovic Courtès
2017-07-31 18:09 ` Dave Love
2017-08-01 9:27 ` Ludovic Courtès
2017-08-01 16:06 ` Dave Love
2017-08-01 17:39 ` Ludovic Courtès
2017-08-01 20:10 ` Dave Love [this message]
2017-08-21 13:17 ` bug#27850: " Ludovic Courtès
2017-08-23 11:08 ` [bug#27850] " Dave Love
2017-08-23 21:34 ` Ludovic Courtès
2017-09-01 10:35 ` Dave Love
2017-09-01 22:10 ` Ludovic Courtès
2017-09-07 16:16 ` Dave Love
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874ltr9hhs.fsf@i-ulialbion.it.manchester.ac.uk \
--to=fx@gnu.org \
--cc=27850@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).