From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-science@gnu.org
Subject: Re: “Tuning packages for a CPU micro-architecture”
Date: Fri, 07 Jan 2022 10:46:25 +0100 [thread overview]
Message-ID: <87o84nc1zi.fsf@inria.fr> (raw)
In-Reply-To: <86pmp44kkn.fsf@gmail.com> (zimoun's message of "Thu, 06 Jan 2022 22:32:08 +0100")
Hello,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Thu, 06 Jan 2022 at 17:22, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
>
>> I’ve found reproducibility to be often depicted as being detrimental to
>> performance in HPC circles, so this is a contribution to suggest
>> otherwise.
>
> Who knows if an “HPC fool” would not write a ’package-with-tune’
> rewriting the ’tune’ properties to all the packages and then run a
> world-rebuild. ;-)
Heh. :-)
> Well, the conscious choice of letting ’--tune’ operates only on packages
> explicitly marked as “tunable” appears to me a clean design. It makes a
> an explicit and clear separation between “portable-optimized” packages
> (almost all) vs “micro-optimized” packages. The best of both worlds: as
> much as possible reproducible, sacrificing for few corner-cases, keeping
> the performance for all.
Yeah, I think so.
A question that remains: even as a “regular user” on my laptop, I use
things that depend for instance on Eigen. Often Eigen is not critical
to the overall performance (and energy efficiency) of those things, but
it still plays its part; it would be tempting from that perspective to
have ‘--tune’ turned on by default. I think it’s too early to take that
route but might be something to consider in the future.
Thanks for your feedback!
Ludo’.
prev parent reply other threads:[~2022-01-07 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 16:22 “Tuning packages for a CPU micro-architecture” Ludovic Courtès
2022-01-06 21:32 ` zimoun
2022-01-07 9:46 ` Ludovic Courtès [this message]
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=87o84nc1zi.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-science@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.
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).