All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <hd@cavy.de>
To: linux-kernel@vger.kernel.org
Cc: Dave Jones <davej@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	mingo@redhat.com
Subject: Re: slowdown with new scheduler.
Date: Mon, 14 Jan 2002 18:20:10 +0100	[thread overview]
Message-ID: <20020114172010.GA173@elfie.cavy.de> (raw)
In-Reply-To: <20020114124541.A32412@suse.de>
In-Reply-To: <20020114124541.A32412@suse.de>

On Mon Jan 14 2002, Dave Jones wrote:

>  After adding H7 to 2.4.18pre3, I noticed that kernel compiles
> on one of my test boxes got much slower.
> Uniprocessor system (Cyrix 3) building a 2.4.18pre3 tree,
> with the same .config, and a distclean before starting the compile.
> 
> 2.4.18pre3        13.38s                       
> 2.4.18pre+H7      17.53s

I did the same; same config, fresh tree, reboot between the test. 
The machine is a (single-processor) AMD K6-2/400 with 256 MB RAM.
Here are the results:

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

Ingo's scheduler rocks, it runs like hell (and is absolutely stable here)  ;)

-- 
# Heinz Diehl, 68259 Mannheim, Germany

  parent reply	other threads:[~2002-01-14 17:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 12:45 slowdown with new scheduler Dave Jones
2002-01-14 13:27 ` Antony Suter
2002-01-14 17:20 ` Heinz Diehl [this message]
2002-01-14 17:26   ` Dave Jones
2002-01-14 19:29   ` Heinz Diehl
2002-01-14 20:42     ` Banai Zoltan
     [not found] <20020114202903.8BA9176330@public.kitware.com>
2002-01-14 21:08 ` Dieter Nützel
2002-01-14 22:40   ` Heinz Diehl
2002-01-14 23:28     ` Robert Love

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=20020114172010.GA173@elfie.cavy.de \
    --to=hd@cavy.de \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.