From: Roger Luethi <rl@hellgate.ch>
To: Thomas Molina <tmolina@cablespeed.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0 performance problems
Date: Tue, 30 Dec 2003 02:25:52 +0100 [thread overview]
Message-ID: <20031230012551.GA6226@k3.hellgate.ch> (raw)
In-Reply-To: <Pine.LNX.4.58.0312291647410.5288@localhost.localdomain>
On Mon, 29 Dec 2003 17:07:46 -0500, Thomas Molina wrote:
> Execution time for the test was:
> real 13m33.482s
> user 0m33.540s
> sys 0m16.210s
>
>
> Under 2.6 top shows:
> user nice system irq softirq iowait idle
> 0.9 0 5.3 0.9 0.3 92.6 0
>
> Execution time for the test was:
> real 22m42.397s
> user 0m37.753s
> sys 0m54.043s
>
> I've done no performance tweaking in either case. Both tests were done
> immediately after boot up with only the top program running in each case.
> I'm not sure what other data would be relevant here. Any thoughts from
> the group would be appreciated.
I bet this is just yet another instance of a problem we've been
discussing on lkml and linux-mm for several months now (although Linus
asking for DMA presumably means it's not as well known as I thought
it was).
Basically, when you need to resort to paging for getting work done on
2.6 you're screwed. Your bk export takes a lot more memory than you
have RAM in your machine, right?
Check the archives for this thread:
2.6.0-test9 - poor swap performance on low end machines
Roger
next prev parent reply other threads:[~2003-12-30 1:26 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 22:07 2.6.0 performance problems Thomas Molina
2003-12-29 22:21 ` Linus Torvalds
2003-12-29 22:58 ` Thomas Molina
2003-12-29 23:04 ` Linus Torvalds
2003-12-30 14:14 ` Thomas Molina
2003-12-30 14:39 ` William Lee Irwin III
2003-12-30 21:14 ` Thomas Molina
2003-12-30 21:23 ` Linus Torvalds
2003-12-31 0:50 ` Thomas Molina
2003-12-31 1:01 ` Linus Torvalds
2003-12-31 1:34 ` Andrew Morton
2003-12-31 11:25 ` bert hubert
2003-12-30 21:35 ` William Lee Irwin III
2003-12-30 23:46 ` Roger Luethi
2003-12-30 18:20 ` Linus Torvalds
2003-12-29 23:14 ` Martin Schlemmer
2003-12-30 5:09 ` William Lee Irwin III
2003-12-30 10:27 ` Thomas Molina
2003-12-29 23:25 ` David B. Stevens
2003-12-29 23:05 ` Thomas Molina
2003-12-29 23:43 ` Martin Schlemmer
2003-12-30 0:17 ` Thomas Molina
2003-12-30 1:23 ` Martin Schlemmer
2003-12-30 1:27 ` Dave Jones
2003-12-30 1:37 ` Martin Schlemmer
2003-12-30 1:40 ` Dave Jones
2003-12-30 1:49 ` Thomas Molina
2003-12-30 2:03 ` Mike Fedyk
2004-01-03 19:37 ` Bill Davidsen
2003-12-30 1:25 ` Roger Luethi [this message]
2003-12-30 1:37 ` Thomas Molina
2003-12-30 19:21 ` Andy Isaacson
2003-12-30 19:40 ` William Lee Irwin III
2003-12-30 22:24 ` Roger Luethi
2003-12-31 0:33 ` Thomas Molina
2003-12-31 10:17 ` Roger Luethi
2003-12-31 11:21 ` Jens Axboe
2003-12-31 21:03 ` Roger Luethi
2004-01-01 1:27 ` Thomas Molina
2004-01-01 10:23 ` Roger Luethi
2004-01-01 23:09 ` Roger Luethi
2004-01-02 10:11 ` Jens Axboe
2003-12-30 1:27 ` Thomas Molina
2003-12-30 2:53 ` Thomas Molina
-- strict thread matches above, loose matches on Subject: below --
2003-12-30 11:41 Samium Gromoff
2004-01-03 19:54 ` Bill Davidsen
[not found] ` <200312300855.00741.edt@aei.ca>
2004-01-05 12:33 ` Samium Gromoff
2004-01-05 15:09 ` Ed Tomlinson
2004-01-06 2:23 ` David Lang
2004-01-06 14:44 ` Samium Gromoff
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=20031230012551.GA6226@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cablespeed.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