From: "Denys" <nuclearcat@nuclearcat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.21 -> 2.6.22 & 2.6.23-rc8 performance regression
Date: Mon, 1 Oct 2007 13:30:52 +0300 [thread overview]
Message-ID: <20071001103026.M59805@nuclearcat.com> (raw)
In-Reply-To: <p73myv36tmz.fsf@bingen.suse.de>
Already i did, and it didn't show real failure point.
On 01 Oct 2007 12:01:24 +0200, Andi Kleen wrote
> "Denys" <nuclearcat@nuclearcat.com> writes:
>
> > by mistake i will miss a point (it can detect bug easily, IF softirq in
> > mpstat 1 will jump up to 30+%. On 2.6.21 it is always staying +-10%, on
> > "buggy" version it jumps up to 100%. Now cause less load at night up to 30-
> > 50%, so on hardware it is not very noticeable (thats why maybe not much
> > feedbacks), i am trying to utilise hardware maximum as possible - so i feel
> > regressions much more.
>
> You could use oprofile to find where the CPU time is spent
>
> -Andi
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next prev parent reply other threads:[~2007-10-01 10:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 14:48 2.6.21 -> 2.6.22 & 2.6.23-rc8 performance regression Denys
2007-09-30 17:48 ` Eric Dumazet
2007-09-30 4:25 ` Nick Piggin
2007-09-30 22:04 ` Denys
2007-10-01 10:01 ` Andi Kleen
2007-10-01 10:30 ` Denys [this message]
2007-10-01 11:14 ` Andi Kleen
2007-10-01 11:52 ` Denys
2007-10-01 11:57 ` Andi Kleen
2007-10-01 12:04 ` Denys
2007-09-30 22:35 ` Denys
2007-10-01 5:59 ` Eric Dumazet
2007-10-01 7:12 ` David Miller
2007-10-01 8:07 ` Denys
2007-10-01 8:20 ` Eric Dumazet
2007-10-01 8:35 ` Eric Dumazet
2007-10-01 12:10 ` Denys
2007-10-01 13:26 ` Denys
2007-10-01 20:10 ` Eric Dumazet
2007-10-01 20:57 ` David Miller
2007-09-30 23:24 ` Denys
2007-10-01 6:43 ` Denys
2007-09-30 18:45 ` Denys
-- strict thread matches above, loose matches on Subject: below --
2007-09-30 15:22 Denys
2007-09-30 17:31 Denys
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=20071001103026.M59805@nuclearcat.com \
--to=nuclearcat@nuclearcat.com \
--cc=andi@firstfloor.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