From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: guix-science@gnu.org
Subject: “Tuning packages for a CPU micro-architecture”
Date: Thu, 06 Jan 2022 17:22:06 +0100 [thread overview]
Message-ID: <87fsq0eswh.fsf@inria.fr> (raw)
Hello there, and happy new year where applicable!
This blog post discusses the new ‘--tune’ option and “package
multi-versioning” as a way of achieving performance without giving up on
reproducibility:
https://hpc.guix.info/blog/2022/01/tuning-packages-for-a-cpu-micro-architecture/
I’ve found reproducibility to be often depicted as being detrimental to
performance in HPC circles, so this is a contribution to suggest
otherwise.
Ludo’.
next reply other threads:[~2022-01-06 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 16:22 Ludovic Courtès [this message]
2022-01-06 21:32 ` “Tuning packages for a CPU micro-architecture” zimoun
2022-01-07 9:46 ` Ludovic Courtès
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=87fsq0eswh.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-science@gnu.org \
/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).