unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix-HPC activity report
Date: Fri, 22 Feb 2019 16:41:23 +0100	[thread overview]
Message-ID: <CAJ3okZ1D_039xVdfuVvPZaFVG16YgEKBvLLf9DA5u4tQnC0NhQ@mail.gmail.com> (raw)
In-Reply-To: <87d0ntm10w.fsf@inria.fr>

Hi Ludo,

Thank you for your precision.

On Fri, 15 Feb 2019 at 18:09, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
>
> zimoun <zimon.toutoune@gmail.com> skribis:
>
> > Well, is it still accurate ?
> > Is Guix binary still slower than other ?
>
> The comment links to
> <http://fftw.org/fftw3_doc/Installation-on-Unix.html>, which reads:
>
>   Enable various SIMD instruction sets. […] FFTW will try to detect at
>   runtime whether the CPU supports these extensions.  That is, you can
>   compile with --enable-avx and the code will still run on a CPU without
>   AVX support.

If I understand well, the claims p.45 of the EasyBuild presentation
[1] should not true any more.
Because there is a factor 2+ with their benchmarks.

[1] https://users.ugent.be/~kehoste/eum18/eum18_easybuild_past_present_future_20180130.pdf


> So I believe the numbers one gets with the ‘fftw’ package in Guix are
> the best one can get because FFTW does the right thing of using the
> right version of its hot functions at run time.  (That said, you can
> redo the benchs, and if this is not the case, it’s a bug! :-))

A benchmark from "our side" should be informative. :-)
But I am not sure that I would like to dive in EasyBuild stuff... ;-)


Thank you again !
All the best,
simon

      reply	other threads:[~2019-02-22 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 13:51 Guix-HPC activity report Ludovic Courtès
2019-02-12 14:11 ` Laura Lazzati
2019-02-12 15:36   ` zimoun
2019-02-12 16:54     ` Ricardo Wurmus
2019-02-13 17:39 ` Pjotr Prins
2019-02-15 17:23   ` Ludovic Courtès
2019-02-14 10:25 ` Marco van Hulten
2019-02-14 14:43   ` Ludovic Courtès
2019-02-14 15:35     ` zimoun
2019-02-15 17:09       ` Ludovic Courtès
2019-02-22 15:41         ` zimoun [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=CAJ3okZ1D_039xVdfuVvPZaFVG16YgEKBvLLf9DA5u4tQnC0NhQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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).