linux-kernel - Re: miserable performance of 2.6.21 under network load

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Jul 2007 14:49:47 -0400
From:	Chris Snook <csnook@...hat.com>
To:	Aaron Porter <atporter@...mate.net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: miserable performance of 2.6.21 under network load

Aaron Porter wrote:
> 	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.

Is it always CPU 0, or does it move?  Are you running irqbalance?  If you're 
running irqbalance, you can run a script that alternates between 'cat 
/proc/interrupts' and 'mpstat -P ALL 5 10' and watch the offending interrupt 
jump around between processors.  It's not as informative as oprofile, as Andi 
suggested, but it's really easy to set up.

	-- Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/