From: Andrew Morton <akpm@osdl.org>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: nathans@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Fw: Performance drop 2.6.0-test7 -> 2.6.1-rc2
Date: Thu, 8 Jan 2004 02:33:56 -0800 [thread overview]
Message-ID: <20040108023356.00db9dec.akpm@osdl.org> (raw)
In-Reply-To: <20040108112547.G20265@fi.muni.cz>
Jan Kasprzak <kas@informatics.muni.cz> wrote:
>
> Andrew Morton wrote:
> : Jan Kasprzak <kas@informatics.muni.cz> wrote:
> : > - this is reliable: repeated boot back to 2.6.1-rc2 makes the problem
> : > appear again (high load, system slow has hell), booting back
> : > to -test7 makes it disappear.
> :
> : Is the CPU load higher than normal? Excluding I/O wait?
>
> No, ~30% system is pretty standard for this server. I have looked
> just now (2.6.0-test7), and I have 33% system, about 50% nice,
> and the rest is user, iowait and idle. Under 2.6.1-rc2 it was about 30%
> system and the rest iowait, with small amount of nice and user.
> However, the load may be different. It is hard to have any kind of
> "fixed" load when you serve data over FTP, HTTP, rsync and do some
> other minor tasks (updatedb, current/up2date server, ...).
OK.
> Do you still want the system profiling info?
Nope.
It would be interesting to run some simple benchmarks (dbench, iozone,
tiobench, etc) on a relatively idle system.
After that, it'd be a matter of searching through kernel versions, which
you presumably cannot do. Or eliminating device mapper from the picture,
which is also presumably not an option.
Have you run `hdparm' to check that all those disks have DMA enabled? I
guess they have.
next prev parent reply other threads:[~2004-01-08 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040107023042.710ebff3.akpm@osdl.org>
2004-01-07 21:52 ` Nathan Scott
2004-01-08 9:54 ` Jan Kasprzak
2004-01-08 10:16 ` Andrew Morton
2004-01-08 10:25 ` Jan Kasprzak
2004-01-08 10:33 ` Andrew Morton [this message]
2004-01-08 11:01 ` Jan Kasprzak
2004-01-08 14:20 ` J. Ryan Earl
2004-01-08 12:07 ` Christoph Hellwig
2004-01-08 15:03 ` Jan Kasprzak
2004-01-08 15:11 ` Jan Kasprzak
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=20040108023356.00db9dec.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
/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