public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: GCC Mailing List <gcc@gcc.gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: LMbench as gcc performance regression test?
Date: Sun, 31 Aug 2003 08:59:10 -0700	[thread overview]
Message-ID: <3F521B4E.10909@kegel.com> (raw)
In-Reply-To: <20030831152449.GA6893@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Sun, Aug 31, 2003 at 12:21:37AM -0700, Dan Kegel wrote:
> 
>>http://cs.nmu.edu/~benchmark/ has an interesting little graph
>>of LMBench results vs. Linux kernel version, all done with the
>>same compiler.
>>
>>Has anyone seen a similar graph showing LMBench results vs. gcc version,
>>all done with the same Linux kernel?
>>And does everyone agree that's a meaningful way to compare the
>>performance of code generated by different compilers?
> 
> It's been a while since I looked at lmbench but: why do you think this
> would be useful?  It's a system and kernel benchmark; I doubt
> optimization makes much difference at all.

I need to make sure that moving to a newer compiler for our kernel
will cause no performance regressions.  Before bothering to bring up a
real-world networking application and measuring its performance
under the new compiler, it seems sensible to use a couple microbenchmarks
to verify that identifiable parts of the system have
not degraded in performance.

I myself am quite convinced I need to move to a newer compiler,
since I keep running into problems building various things with
old compilers, but my users are very conservative and skeptical;
I have to build a solid case for updating.  Hence the insane amount
of time I spent figuring out and documenting how to build and test
the various versions of gcc and glibc (http://kegel.com/crosstool),
and then understanding the regression test failures.
- Dan

-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


  reply	other threads:[~2003-08-31 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31  7:21 LMbench as gcc performance regression test? Dan Kegel
2003-08-31 14:00 ` Larry McVoy
2003-08-31 14:28   ` Dan Kegel
     [not found]   ` <3F520773.1070907@kegel.com>
     [not found]     ` <20030831145956.GE23783@work.bitmover.com>
2003-08-31 22:53       ` Dan Kegel
2003-08-31 15:24 ` Daniel Jacobowitz
2003-08-31 15:59   ` Dan Kegel [this message]
2003-08-31 16:18     ` Larry McVoy
2003-08-31 17:03 ` Martin J. Bligh
  -- strict thread matches above, loose matches on Subject: below --
2003-08-31 16:57 rwhron

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=3F521B4E.10909@kegel.com \
    --to=dank@kegel.com \
    --cc=dan@debian.org \
    --cc=gcc@gcc.gnu.org \
    --cc=linux-kernel@vger.kernel.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