public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Wilco Dijkstra <wilco@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Benchtests: Increase benchmark iterations
Date: Fri, 12 Jan 2024 16:09:30 +0000 (GMT)	[thread overview]
Message-ID: <20240112160930.B275F3858407@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7c14d8a985416986256f68568313cdb36f559821

commit 7c14d8a985416986256f68568313cdb36f559821
Author: Wilco Dijkstra <wilco.dijkstra@arm.com>
Date:   Tue Jan 2 17:08:02 2024 +0000

    Benchtests: Increase benchmark iterations
    
    Increase benchmark iterations for math and vector math functions to improve
    timing accuracy.  Vector math benchmarks now take 1-3 seconds on a modern CPU.
    
    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

Diff:
---
 benchtests/bench-libmvec-skeleton.c | 2 +-
 benchtests/bench-skeleton.c         | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/benchtests/bench-libmvec-skeleton.c b/benchtests/bench-libmvec-skeleton.c
index d75519cb79..fa328ac932 100644
--- a/benchtests/bench-libmvec-skeleton.c
+++ b/benchtests/bench-libmvec-skeleton.c
@@ -29,7 +29,7 @@
 #include <bench-libmvec-arch.h>
 
 #include <bench-util.c>
-#define D_ITERS 10000
+#define D_ITERS 200000
 
 int
 main (int argc, char **argv)
diff --git a/benchtests/bench-skeleton.c b/benchtests/bench-skeleton.c
index 83060c9cfa..60add3f3f3 100644
--- a/benchtests/bench-skeleton.c
+++ b/benchtests/bench-skeleton.c
@@ -48,7 +48,7 @@ main (int argc, char **argv)
 
   memset (&runtime, 0, sizeof (runtime));
 
-  unsigned long iters = 1000;
+  unsigned long iters = 2000;
 
 #ifdef BENCH_INIT
   BENCH_INIT ();

                 reply	other threads:[~2024-01-12 16:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240112160930.B275F3858407@sourceware.org \
    --to=wilco@sourceware.org \
    --cc=glibc-cvs@sourceware.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).