netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: herbert@gondor.apana.org.au, cl@linux-foundation.org,
	netdev@vger.kernel.org
Subject: Re: AIM9 regression
Date: Wed, 24 Sep 2008 12:36:57 -0700 (PDT)	[thread overview]
Message-ID: <20080924.123657.217162945.davem@davemloft.net> (raw)
In-Reply-To: <20080924081603.08a5f808@extreme>

From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 24 Sep 2008 08:16:03 -0700

> On Tue, 23 Sep 2008 22:18:31 -0700 (PDT)
> David Miller <davem@davemloft.net> wrote:
> 
> > From: Herbert Xu <herbert@gondor.apana.org.au>
> > Date: Wed, 24 Sep 2008 13:12:37 +0800
> > 
> > > On Tue, Sep 23, 2008 at 01:14:27PM -0500, Christoph Lameter wrote:
> > > > I just dont seem to be able to get 2.6.27 to behave in a speedy way network
> > > > wise. Configured out various components (netfilter, etc etc) but I still keep
> > > > getting these aim9 result against 2.6.22:
> > > 
> > > Could you please compare this against something less ancient,
> > > like 2.6.26 perhaps?
> > 
> > Herbert, this is part of the tbench regression issues.  Christoph
> > took tbench from 2.6.22 until 2.6.27 and at basically every release
> > tbench performance suffered noticably.
> > 
> > Now, he's taking the AIM9 benchmark networking numbers and showing
> > that the same exact effect is seen there too.
> > 
> > It really behooves us to start doing something proactive about this
> > blindingly obvious set of networking performance regressions through
> > the past 6 or so releases instead of barking at the reporters saying
> > things like "try this, try that, what's your config" etc.
> > 
> > :-)
> 
> These loopback benchmarks are often more sensitive to scheduler than networking
> changes.

When it gets to %20, I strong start to doubt that, and this is exactly
what's happening here.

What is it going to take to actually get someone to start profiling and
analyzing this?  :-)


  parent reply	other threads:[~2008-09-24 19:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 18:14 AIM9 regression Christoph Lameter
2008-09-23 20:36 ` Stephen Hemminger
2008-09-23 20:40   ` Christoph Lameter
2008-09-23 20:43     ` Christoph Lameter
2008-09-24  1:20     ` Jeff Garzik
2008-09-24  3:11       ` David Miller
2008-09-24 14:20         ` Christoph Lameter
2008-09-24  5:12 ` Herbert Xu
2008-09-24  5:18   ` David Miller
2008-09-24 15:16     ` Stephen Hemminger
2008-09-24 19:10       ` Christoph Lameter
2008-09-24 19:53         ` David Miller
2008-09-24 21:34           ` Stephen Hemminger
2008-09-24 22:26             ` David Miller
2008-09-24 19:36       ` David Miller [this message]
2008-09-29 14:24         ` Ilpo Järvinen
2008-09-29 14:54           ` Christoph Lameter
2008-09-29 15:12             ` Ilpo Järvinen
2008-09-29 15:36             ` Stephen Hemminger
2008-10-31 14:57             ` Ilpo Järvinen

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=20080924.123657.217162945.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cl@linux-foundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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 NNTP newsgroup(s).