unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Guix-devel <guix-devel@gnu.org>, Eric Bavier <bavier@cray.com>,
	Dave Love <fx@gnu.org>, Federico Beffa <beffa@ieee.org>
Subject: Re: OpenBLAS and performance
Date: Fri, 22 Dec 2017 17:08:25 +0100	[thread overview]
Message-ID: <20171222160825.GA20709@thebird.nl> (raw)
In-Reply-To: <87tvwi94sw.fsf@inria.fr>

On Fri, Dec 22, 2017 at 04:10:39PM +0100, Ludovic Courtès wrote:
> Static binding has a cost, as you write, but it gives us control over
> the environment, and the ability to capture and replicate the software
> environment.  As a user, that’s something I value a lot.

> I’d also argue that this is something computational scientists should
> value: first because results they publish should not depend on the phase
> of the moon, second because they should be able to provide peers with a
> self-contained recipe to reproduce them.

As a scientist I value that *more* than a lot. There is a tension
between 'just getting things done' and making things reproducible. If
we can do the latter, we should.  Also as a programmer I value
reproducibility a lot. I want people who report bugs to use the exact
same setup. Especially when they are running on machines I can not
access (quite common in sequencing centers). If someone sends me a
core dump, stack trace or even an asserting in a shared lib it is
incredibly useful the full stack is the same.

I am wary of flexible resolution of optimized libraries and kernels.
Look at what atlas tried to do and what a mess it became. I strongly
believe we need explicit statements about what we are running. It does
imply Guix will have to provide all options, directly or through
channels.

I also work on HPC and if I know where I am running I know *what* to
target. It is a deterministic recipe. 

Pj.

      reply	other threads:[~2017-12-22 16:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 10:49 OpenBLAS and performance Pjotr Prins
2017-12-19 17:12 ` Ludovic Courtès
2017-12-20 11:50 ` Dave Love
2017-12-20 14:48   ` Dave Love
2017-12-20 15:06     ` Ricardo Wurmus
2017-12-22 12:24       ` Dave Love
2017-12-20 17:22     ` Pjotr Prins
2017-12-20 18:15       ` Ricardo Wurmus
2017-12-20 19:28         ` Pjotr Prins
2017-12-20 20:00           ` Ricardo Wurmus
2017-12-20 20:32             ` Pjotr Prins
2017-12-20 19:02               ` Eric Bavier
2017-12-21 16:38                 ` Dave Love
2017-12-20 23:02               ` Ricardo Wurmus
2017-12-21 10:36                 ` Pjotr Prins
2017-12-21 14:43           ` Ludovic Courtès
2017-12-22 14:35           ` Dave Love
2017-12-21 16:17         ` Dave Love
2017-12-21 16:46           ` Ricardo Wurmus
2017-12-21 14:55   ` Ludovic Courtès
2017-12-22 12:45     ` Dave Love
2017-12-22 15:10       ` Ludovic Courtès
2017-12-22 16:08         ` Pjotr Prins [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=20171222160825.GA20709@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=bavier@cray.com \
    --cc=beffa@ieee.org \
    --cc=fx@gnu.org \
    --cc=guix-devel@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).