public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Will Newton <will.newton@linaro.org>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
	"libc-ports@sourceware.org" <libc-ports@sourceware.org>,
	"Ondřej Bílka" <neleai@seznam.cz>,
	libc-alpha <libc-alpha@sourceware.org>
Subject: Re: benchmark improvements (Was: Re: [PATCH] sysdeps/arm/armv7/multiarch/memcpy_impl.S: Improve performance.)
Date: Tue, 03 Sep 2013 13:46:00 -0000	[thread overview]
Message-ID: <CANu=DmgDYv0JFxqCYUkL2iz_GTSm0LKJvmtGD_i04wB=qDvu7A@mail.gmail.com> (raw)
In-Reply-To: <20130902142037.GH3273@spoyarek.pnq.redhat.com>

On 2 September 2013 15:20, Siddhesh Poyarekar <siddhesh@redhat.com> wrote:
> Adding libc-alpha since my comments on this are more suitable there -
> maybe we should just get rid of the ports mailing list altogether.
>
> On Mon, Sep 02, 2013 at 02:58:23PM +0100, Will Newton wrote:
>> The key advantage of the cortex-strings framework is that it allows
>> graphing the results of benchmarks. Often changes to string function
>> performance can only really be analysed graphically as otherwise you
>> end up with a huge soup of numbers, some going up, some going down and
>> it is very hard to separate the signal from the noise.
>
> We already depend on gd-devel to draw graphs for memusagestat.  Maybe
> we could leverage that in the microbenchmark as well and come up with
> html reports rather than just a bench.out?  Graphs in general are a
> lot more readable and I agree that they would be the next logical
> improvement to the benchmark framework.

gd is quite basic from a graph plotting point of view, it's more of a
low-level graphics library and requires wrappers to call from
scripting languages. I already have some code I can cannibalize from
cortex-strings that uses Python and Pylab to do the plotting, I'll
submit a patch for review soon.

>> The glibc benchmarks also have some other weaknesses that should
>> really be addressed, hopefully I'll have some time to write patches
>> for some of this work.
>
> I know Ondrej had proposed a few improvements as well.  I'd like to
> see those reposted so that we can look at it and if possible, have
> them merged in.

I already have a patch to do multiple runs of benchmarks  - some
things like physical page allocation that can impact a benchmark can
only be controlled for this way. As I mentioned above I'd also like to
get graphing capability in there too. Beyond that it would be nice to
have a look at the various sizes and alignments used and make sure
there is a reasonably complete set, and to make sure the tests are run
for a useful number of iterations (not too large or too small).


-- 
Will Newton
Toolchain Working Group, Linaro

  reply	other threads:[~2013-09-03 13:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12  7:55 [PATCH] sysdeps/arm/armv7/multiarch/memcpy_impl.S: Improve performance Will Newton
2013-08-27  7:46 ` Will Newton
2013-08-30 17:14   ` Carlos O'Donell
2013-08-30 18:48     ` Will Newton
2013-08-30 19:26       ` Carlos O'Donell
2013-09-02 14:18         ` Will Newton
2013-09-03 16:14           ` Carlos O'Donell
     [not found]         ` <CANu=DmhA9QvSe6RS72Db2P=yyjC72fsE8d4QZKHEcNiwqxNMvw@mail.gmail.com>
2013-09-02 14:18           ` benchmark improvements (Was: Re: [PATCH] sysdeps/arm/armv7/multiarch/memcpy_impl.S: Improve performance.) Siddhesh Poyarekar
2013-09-03 13:46             ` Will Newton [this message]
2013-09-03 17:48               ` Ondřej Bílka
2013-09-02 19:57           ` [PATCH] sysdeps/arm/armv7/multiarch/memcpy_impl.S: Improve performance Ondřej Bílka
2013-09-03 16:18           ` Carlos O'Donell
2013-09-03 17:37             ` Ondřej Bílka
2013-09-03 17:52               ` Carlos O'Donell
2013-09-03 18:57                 ` Ondřej Bílka
2013-09-03 19:15                   ` Carlos O'Donell
2013-09-04  7:27                     ` Siddhesh Poyarekar
2013-09-04 11:03                       ` Ondřej Bílka
2013-09-04 11:43                         ` Siddhesh Poyarekar
2013-09-04 17:37                         ` Ryan S. Arnold
2013-09-05  8:04                           ` Ondřej Bílka
2013-09-04 15:30                       ` Carlos O'Donell
2013-09-04 17:35                       ` Ryan S. Arnold
2013-09-05 11:07                         ` Ondřej Bílka
2013-09-05 11:54                         ` Joseph S. Myers
2013-09-03 19:34               ` Ryan S. Arnold
2013-09-07 11:55                 ` Ondřej Bílka
2013-09-03 19:31             ` Ryan S. Arnold
2013-09-03 19:54               ` Carlos O'Donell
2013-09-03 20:56                 ` Ryan S. Arnold
2013-09-03 23:29                   ` Ondřej Bílka
2013-09-03 23:31                   ` Carlos O'Donell
2013-09-03 22:27               ` Ondřej Bílka
2013-08-29 23:58 ` Joseph S. Myers
2013-08-30 14:56   ` Will Newton
2013-08-30 15:18     ` Joseph S. Myers
2013-08-30 18:46       ` Will Newton

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='CANu=DmgDYv0JFxqCYUkL2iz_GTSm0LKJvmtGD_i04wB=qDvu7A@mail.gmail.com' \
    --to=will.newton@linaro.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=neleai@seznam.cz \
    --cc=siddhesh@redhat.com \
    /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).