From: Thomas Molina <tmolina@cablespeed.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0 performance problems
Date: Tue, 30 Dec 2003 19:50:24 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.58.0312301938060.3193@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0312301318540.2065@home.osdl.org>
On Tue, 30 Dec 2003, Linus Torvalds wrote:
> Ok. This looks much closer to the 2.4.x numbers you reported:
>
> real 13m50.198s
> user 0m33.780s
> sys 0m15.390s
>
> so I assume that we can consider this problem largely solved? There's
> still some difference, that could be due to just VM tuning..
>
> I suspect that what happened is:
> - slab debugging adds a heavy CPU _and_ it also makes all the slab caches
> much less dense.
> - as a result, you see much higher system times, and you also end up
> needing much more memory for things like the dentry cache, so your
> memory-starved machine ended up swapping a lot more too.
So you are telling me that I am paying the price for running development
kernels and enabling all the debugging. I enjoy running the development
stuff and testing new stuff. I enabled all the kernel hacking and
debugging options with the idea it might be useful for testing purposes.
Disabling all the debugging stuff brings the numbers down, but things
still "feel" worse. It's subjective, but there you are. I'll continue to
test with whatever provides the most useful data.
next prev parent reply other threads:[~2003-12-31 0:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 22:07 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 [this message]
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
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
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=Pine.LNX.4.58.0312301938060.3193@localhost.localdomain \
--to=tmolina@cablespeed.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®