From: "Martin J. Bligh" <mbligh@google.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, apw@shadowen.org
Subject: Re: Clear performance regression on reaim7 in 2.6.15-git6
Date: Sat, 15 Apr 2006 14:31:02 -0700 [thread overview]
Message-ID: <44416616.10908@google.com> (raw)
In-Reply-To: <20060415141744.042231a8.akpm@osdl.org>
Andrew Morton wrote:
> "Martin J. Bligh" <mbligh@google.com> wrote:
>
>>OK, looking back through the perf results, these two graphs clearly show
>>a perf regression in reaim7 from 2.6.15 to 2.6.16-rc1. We're loosing
>>over 50% of the performance.
>>
>>http://test.kernel.org/abat/perf/reaim.moe.png
>>http://test.kernel.org/abat/perf/reaim.elm3b67.png
>
> Something very bad has allegedly been happening in -mm. It would have been
> nice to have heard about this problem in that multi-month wwindow there.
> Does no human look at these numbers?
Obviously not ;-(
I do look every so often, but not frequently. I'm working on
reformatting the site right now, which is why I was poking around.
reaim I often don't look at, as it's not as stable as I'd like, but
that is a *huge* drop.
You can see I collated stuff down into a collection of tests per
machine-release combo, so the dbench and LTP results are folded
into the main matrix now. Next stage is to add performance regression
comparions in there, but it's not easy unless we run multiple times
so that I get std dev as well as average. All of this should make it
easier to (a) see and (b) send out proactive notifications.
>>Drilling down (there's not enough detail on the graphs for releases that
>>far back), I see it's actually between -git5 and -git6
>>
>>These are both ia-32 NUMA machines, one is an x440, the other is NUMA-Q.
>
>
> The 2.6.15-git5 -> 2.6.15-git6 diff is enormous. I'd assume some bad thing
> got transferred into mainline then.
>
> How does one reproduce this? Which type of filesystem, which command
> line/config file?
Sigh ... this is exactly why I want the new autotest harness, I could
just hand you the control file and you could run the same test (at your
box or OSDL or whatever). Not finished yet though ;-(
drilling down into the results directories can get you the command line,
looks like "reaim -f workfile.short -s 1 -e 10 -i 2" to me. Buggered if
I can recall what that did though.
(http://test.kernel.org/abat/20229/004.reaim.test/results/cmdline)
I *think* it's only ia32 NUMA boxes, at least as far as I can see from
a quick poke around. Which would make me guess at scheduler code. Gitweb
would be nice to use, but it doesn't tag the -git snapshots, AFAICS,
which is a real shame. Nor does the git snapshot include the git tag,
as far as I know. Grrrr. I guess I'll download the snapshots and diff
them, and try to pull out the sched changes by hand. Much suckage.
M.
next prev parent reply other threads:[~2006-04-15 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 19:10 Clear performance regression on reaim7 in 2.6.15-git6 Martin J. Bligh
2006-04-15 21:17 ` Andrew Morton
2006-04-15 21:31 ` Martin J. Bligh [this message]
2006-04-15 21:52 ` Andrew Morton
2006-04-15 22:30 ` Martin J. Bligh
2006-04-15 22:45 ` Andrew Morton
2006-04-15 22:59 ` Martin J. Bligh
2006-04-15 23:28 ` Martin J. Bligh
2006-04-15 22:56 ` OGAWA Hirofumi
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=44416616.10908@google.com \
--to=mbligh@google.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.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