From: "Brent" <brent@skyblue.eu.org>
To: <linux-kernel@vger.kernel.org>
Subject: High load since upgrade
Date: Fri, 9 Dec 2005 11:57:37 -0000 [thread overview]
Message-ID: <000001c5fcb7$c006e820$030c0b0a@mforma.com> (raw)
Hi
Hope this is the right list I'm posting to but here goes.
I recently upgraded 3 servers to the stock 2.6.14.3 kernels from an older
2.4.28 kernel, all identical running debian stable and all up to date with
no outstandng updates needed to the OS.
As from these 3 graphs (all servers almost identical hardware), PIII 900, 1G
RAM, you can quite clearly see when the upgrades where made and sending the
load avg up way above the previous averages.
http://pics.skyblue.eu.org/graphs/
All these servers are only running; shorewall, squid and ntop as their
primary functions.
Before I go pasting my .config etc etc I wanted to know first off what
anyone would really like so I don't paste too much to create a really large
post. Also if it's a known issue?
But here is a quick vmstat and as can see the 'in' is rather larger than
normal I would think?
Top is not reporting anything usefull really.
/usr/src/linux-2.6.14.3# vmstat -n 1
procs -----------memory---------- ---swap-- -----io---- --system--
----cpu----
r b swpd free buff cache si so bi bo in cs us sy id
wa
0 0 0 26 231 364 0 0 0 13 13 4 1 2 97
0
0 0 0 26 231 364 0 0 0 0 272 42 0 0 100
0
0 0 0 26 231 364 0 0 0 0 265 35 0 0 100
0
0 0 0 26 231 364 0 0 0 0 276 46 0 0 100
0
0 0 0 26 231 364 0 0 0 36 290 70 0 0 100
0
0 0 0 26 231 364 0 0 0 48 276 64 0 0 100
0
0 0 0 26 231 364 0 0 0 0 291 69 0 0 100
0
0 0 0 26 231 364 0 0 0 12 266 37 0 0 100
0
0 0 0 26 231 364 0 0 0 0 315 120 0 0 100
0
0 0 0 26 231 364 0 0 0 4 322 116 0 0 100
0
0 0 0 26 231 364 0 0 0 0 313 99 0 0 100
0
0 0 0 26 231 364 0 0 0 0 301 92 0 0 100
0
0 0 0 26 231 364 0 0 0 0 279 49 0 0 100
0
0 0 0 26 231 364 0 0 0 0 298 77 0 0 100
0
0 0 0 26 231 364 0 0 0 0 315 93 0 0 100
0
0 0 0 26 231 364 0 0 0 36 300 74 0 0 100
0
0 0 0 26 231 364 0 0 0 0 283 45 0 0 100
0
A list of the hardware is from lspci is:
0000:00:00.0 Host bridge: ServerWorks CNB20HE Host Bridge (rev 23)
0000:00:00.1 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
0000:00:00.2 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
0000:00:00.3 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
0000:00:01.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
0000:00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
0000:00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev
27)
0000:00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 50)
0000:00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller
0000:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev
04)
0000:01:04.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev
05)
0000:02:00.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev
05)
0000:02:01.0 SCSI storage controller: QLogic Corp. ISP12160 Dual Channel
Ultra3 SCSI Processor (rev 06)
0000:03:00.0 RAID bus controller: American Megatrends Inc. MegaRAID (rev 20)
0000:04:05.0 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
0000:04:05.1 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
0000:04:06.0 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet
Controller (rev 03)
0000:04:06.1 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet
Controller (rev 03)
next reply other threads:[~2005-12-09 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 11:57 Brent [this message]
2005-12-09 21:44 ` Willy Tarreau
2005-12-11 12:54 ` Brent
2005-12-11 13:08 ` Willy Tarreau
2005-12-11 17:06 ` Brent
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='000001c5fcb7$c006e820$030c0b0a@mforma.com' \
--to=brent@skyblue.eu.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
Powered by JetHome