From: Yven Leist <leist@beldesign.de>
To: "James M." <Dart@windeath.2y.net>
Cc: linux-kernel@vger.kernel.org, Michael Cohen <me@ohdarn.net>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.4.19-preX: What we really need: -AA patches finally in the tree
Date: Thu, 7 Mar 2002 00:34:13 +0100 [thread overview]
Message-ID: <20020306233414.4A00D2ADE29@fastpage.beldesign.net> (raw)
In-Reply-To: <E16iPsR-00052J-00@the-village.bc.nu> <3C8574C9.E1E4688C@windeath.2y.net>
In-Reply-To: <3C8574C9.E1E4688C@windeath.2y.net>
On Wednesday 06 March 2002 02:45, James M. wrote:
> Alan Cox wrote:
> > > I won't bring it up again, I'd love to think Rik, Alan and Ingo will
> > > keep working on performance patches for 2.4, but I wouldn't bet on it.
> >
> > I certainly will work on collating them - over time it will get less and
> > less of a win. A lot of the now very visible ones are really hard to fix
> > in 2.4 and will be 2.5 things (like block). And when you fix block you'll
> > find the next one and so on forever
>
> I'd love to see some performance patches. I've been watching my quake
> "timerefreshes" drop since 2.2. I've been using Ingo's scheduler patches
> on 2.4.17 with vast improvements in "smoothness" with what seems like an
> occasional block on big writes. I also tried 2.4.19-pre2-ac2(with
> scheduler merged), in that case the smoothness wasn't quite so apparent
> even with X niced to -10. There were also a lot of sound skips that
> didn't happen with 2.4.17/sched-K3. I attributed those to the renicing
> of X to smooth out the mouse.
I can really recommend 2.4.18-pre9-mjc2; it's _much_ better than
2.4.18-pre8-mjc (I guess that's the difference between K2 and K3) and gives
great interactive feel. I had it running continously for almost 20 days now
and I've beaten it like hell, with vmware, wine, heavily threaded java apps,
etc.. While doing really crazy things like "make -j 200" on my lowend athlon
with 640MB RAM, the system remains 100% responsive, and this with a load well
over 200 and more than 1000 processes!!
Where these "performance" enhancements are really getting invaluable, is when
you do things like opening 1000 mp3 files in konqueror thinking you had
"allow multiple instances" disabled in xmms... ;
the stock 2.4 kernel just falls flat in such a situation, not even giving you
the possibility to switch to the console to type "killall xmms" :-)
so all these "performance" patches (especially the scheduler of course) do
have invaluable benefits even for normal users with UP systems, and are
therefore, IMHO of course, worth being integrated into 2.4 mainline.
cheers,
Yven
P.S: thanks for all the fantastic work :-)
--
Yven Johannes Leist - leist@beldesign.de
http://www.leist.beldesign.de
next prev parent reply other threads:[~2002-03-06 23:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 6:41 dart
2002-03-05 21:49 ` Bill Davidsen
2002-03-06 1:05 ` Alan Cox
2002-03-06 1:45 ` James M.
2002-03-06 16:50 ` Ken Brownfield
2002-03-07 10:11 ` Leonid Mamtchenkov
2002-03-06 23:34 ` Yven Leist [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 0:35 Dieter Nützel
2002-02-26 1:02 ` Ken Brownfield
2002-02-26 1:13 ` Andrew Morton
2002-02-26 7:20 ` Jens Axboe
2002-02-26 1:39 ` Alan Cox
2002-02-26 1:15 ` Shawn Starr
2002-02-26 8:36 ` Christoph Rohland
2002-02-26 1:32 ` Martin J. Bligh
2002-02-24 5:44 ` Daniel Phillips
2002-02-26 4:33 ` Martin J. Bligh
2002-02-26 11:42 ` Rik van Riel
2002-02-26 1:40 ` Rik van Riel
2002-02-26 1:49 ` Martin J. Bligh
2002-02-26 1:51 ` Alan Cox
2002-02-26 7:07 ` Christoph Hellwig
2002-02-26 16:21 ` Mike Fedyk
2002-02-26 16:53 ` Christoph Hellwig
2002-02-28 22:45 ` Bill Davidsen
2002-02-28 23:04 ` Rik van Riel
2002-03-01 3:02 ` Bill Davidsen
2002-03-01 3:13 ` Rik van Riel
2002-03-01 3:43 ` Davide Libenzi
2002-03-01 10:36 ` Sean Hunter
2002-03-01 17:13 ` Davide Libenzi
2002-03-01 6:29 ` Olivier Galibert
2002-03-01 16:28 ` Dan Chen
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=20020306233414.4A00D2ADE29@fastpage.beldesign.net \
--to=leist@beldesign.de \
--cc=Dart@windeath.2y.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@ohdarn.net \
--cc=mingo@elte.hu \
/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®