all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Felix Gruber <felgru@posteo.net>
Cc: 53121-done@debbugs.gnu.org
Subject: [bug#53121] [PATCH] gnu: ceres: Update to 2.0.0.
Date: Wed, 19 Jan 2022 11:26:54 +0100	[thread overview]
Message-ID: <87y23caump.fsf@gnu.org> (raw)
In-Reply-To: <b7bbebe1-c956-4182-9272-48b1f798fa60@posteo.net> (Felix Gruber's message of "Tue, 18 Jan 2022 12:39:42 +0000")

Hi,

Felix Gruber <felgru@posteo.net> skribis:

> Unfortunately, I'm getting mixed results for the benchmarks. In most
> cases, I got slight (<10%) improvements in runtime, but there are also 
> some benchmarks that were worse with the --tune flag. I'm wondering
> whether the compiler flags set by the --tune option are correctly used 
> by the custom 'build phase of the ceres-solver-benchmarks package. I
> didn't have the time to look closer into it as I'm currently in the 
> middle of moving to another country.

OK.

> Anyways, I've attached the results of benchmark runs that I've
> generated using guix commit 7f779286df7e8636d901f4734501902cc934a72f
> once untuned and once tuned for broadwell CPUs.
> My laptop on which I ran the tests has a Quad Core AMD Ryzen 7 PRO
> 2700U CPU with 2200 MHz.

Could it be that ‘znver3’ or something works better on those CPUs?

> In the attachments you find
> * a script run_benchmarks.sh used to run the benchmarks in tuned and
>   untuned guix shells,
> * text files ending in `-tuned` or `-untuned` which contain the
>   results of those benchmark runs,
> * a script compare.sh which calls a Python script compare-results.py
>   to generate files ending in `-diff` that contain the relative change 
> between untuned and tuned benchmarks (negative time and CPU
> percentages mean the tuned benchmark was faster, while for the number
> of iterations, positive percentages mean the tuned benchmark had run
> more iterations).

Interesting, thanks for taking the time to run these benchmarks.

It’s hard to draw conclusions.  I wonder how noisy these measurements
are and whether the differences we’re seeing are significant.  Food for
thoughts!

Ludo’.




      reply	other threads:[~2022-01-19 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 22:02 [bug#53121] [PATCH] gnu: ceres: Update to 2.0.0 Felix Gruber
2022-01-11 19:10 ` bug#53121: " Ludovic Courtès
2022-01-18 12:39   ` [bug#53121] " Felix Gruber
2022-01-19 10:26     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y23caump.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53121-done@debbugs.gnu.org \
    --cc=felgru@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.