From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Banai Zoltan <bazooka@enclavenet.hu>
Cc: Heinz Diehl <hd@cavy.de>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: slowdown with new scheduler.
Date: Mon, 14 Jan 2002 22:08:23 +0100 [thread overview]
Message-ID: <20020114211010Z289070-13997+4807@vger.kernel.org> (raw)
In-Reply-To: <20020114202903.8BA9176330@public.kitware.com>
In-Reply-To: <20020114202903.8BA9176330@public.kitware.com>
On Monday, 14. January 2002 20:42, you wrote:
> On Mon, Jan 14, 2002 at 08:29:25PM +0100, Heinz Diehl wrote:
> > On Mon Jan 14 2002, Heinz Diehl wrote:
> >
> > > 2.4.18-pre3 real 7m55.243s
> > > user 6m34.080s
> > > sys 0m27.610s
> > >
> > > 2.4.18-pre+H7 real 7m35.962s
> > > user 6m34.270s
> > > sys 0m27.700s
> > >
> > > 2.4.18-pre3-ac2 real 7m39.203s
> > > user 6m34.110s
> > > sys 0m28.740s
> > >
> >
> > 2.4.18-pre3+H7+preempt-rml real 6m58.983s
> > user 6m34.500s
> > sys 0m27.820s
> >
> That sounds very good! But what about the VM code?
> Is the VM in 2.4.18-pre3+H7 as good as in 2.4.18-pre2aa2?
Of course _NOT_.
This is like apples and oranges...
You _must_ compare
2.4.18-pre3+H7+ -aa vm-22 from 2.4.18-pre2aa2
with
2.4.18-pre3+H7+ -rmap
After that you should apply preempt+locl-break or LL to both.
Have a look into Re: [2.4.17/18pre] VM and swap - it's really unusable
Greetings,
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de
next parent reply other threads:[~2002-01-14 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020114202903.8BA9176330@public.kitware.com>
2002-01-14 21:08 ` Dieter Nützel [this message]
2002-01-14 22:40 ` Heinz Diehl
2002-01-14 23:28 ` Robert Love
2002-01-14 12:45 Dave Jones
2002-01-14 13:27 ` Antony Suter
2002-01-14 17:20 ` Heinz Diehl
2002-01-14 17:26 ` Dave Jones
2002-01-14 19:29 ` Heinz Diehl
2002-01-14 20:42 ` Banai Zoltan
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=20020114211010Z289070-13997+4807@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=bazooka@enclavenet.hu \
--cc=hd@cavy.de \
--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