Re: slowdown with new scheduler.
Dieter =?ISO-8859-15?q?N=FCtzel?= (Dieter.Nuetzel@hamburg.de)
Mon, 14 Jan 2002 22:08:23 +0100
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/