From: Chris Snook <csnook@redhat.com>
To: Aaron Porter <atporter@primate.net>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: miserable performance of 2.6.21 under network load
Date: Tue, 24 Jul 2007 15:22:56 -0400 [thread overview]
Message-ID: <46A65190.8070600@redhat.com> (raw)
In-Reply-To: <20070724184908.GD24543@primate.net>
Aaron Porter wrote:
> On Tue, Jul 24, 2007 at 08:48:00PM +0200, Andi Kleen wrote:
>> Aaron Porter <atporter@primate.net> writes:
>>
>>> I'm in the process up upgrading a pool of apache servers from
>>> 2.6.17.8 to 2.6.21.5, and we're seeing a pretty major change in behavior.
>>> Under identical network load, 2.6.21 has a load average more than 3 times
>>> higher, cpu 0 spends well over 90% of its time in interrupts (vs ~30%
>>> under 2.6.17). When we hit 3k apache sessions, ksoftirqd eats 100% of cpu0
>>> and our network traffic drops off rapidly. The end result is that 2.6.17
>>> performs twice as well under this load.
>> Can you oprofile it?
>
> # opreport -l
> CPU: AMD64 processors, speed 1994.52 MHz (estimated)
> Counted CPU_CLK_UNHALTED events (Cycles outside of halt state) with a unit mask of 0x00 (No unit mask) count 100000
> samples % app name symbol name
> 914379 48.8404 vmlinux-2.6.21.5 check_poison_obj
> 341920 18.2632 vmlinux-2.6.21.5 poison_obj
I bet you have CONFIG_DEBUG_SLAB turned off in your 2.6.17 kernel, and turned on
in your 2.6.21 kernel.
-- Chris
next prev parent reply other threads:[~2007-07-24 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 17:25 miserable performance of 2.6.21 under network load Aaron Porter
2007-07-24 18:48 ` Andi Kleen
2007-07-24 18:49 ` Aaron Porter
2007-07-24 19:13 ` Jeff Garzik
2007-07-24 19:13 ` Andi Kleen
2007-07-24 20:41 ` Aaron Porter
2007-07-24 19:22 ` Chris Snook [this message]
2007-07-24 19:45 ` David Miller
2007-07-24 18:49 ` Chris Snook
2007-07-24 18:53 ` Aaron Porter
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=46A65190.8070600@redhat.com \
--to=csnook@redhat.com \
--cc=andi@firstfloor.org \
--cc=atporter@primate.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.