mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: jim.houston@attbi.com
Cc: linux-kernel@vger.kernel.org, jim.houston@ccur.com
Subject: Re: [PATCH] self tuning scheduler
Date: Tue, 11 Mar 2003 10:46:05 +0100	[thread overview]
Message-ID: <5.2.0.9.2.20030311095954.01f9a008@pop.gmx.net> (raw)
In-Reply-To: <200303110030.h2B0UsR00844@linux.local>

Greetings,

I took your patch out for a test-drive, and it appears to have starvation 
problems with irman's process load (dang thing seems to be HELL on schedulers).

Irman starts a load (defaults to 9 tasks passing data in a pipe ring), and 
forks a child which pingpongs one character back and forth to the parent 
for 1000000 iterations, measuring response time for each iteration and 
computing statistics.  With an iteration % 1000 printf() in the evaluation 
routine, I see it start off nice and fast, then begins to get starved for 
up to 30 seconds.  It jerks around for a bit, then slows down to a ~stable 
1 sec/iteration after approximately 300000 iterations.  The whole test 
takes ~2minutes with 2.5.64-virgin.  (I'm not patient enough to wait for 
the rest of the .5million iterations left on this burn before reporting:)

It also shows a serious throughput loss with make -j30 bzImage on this box 
(I think you expect that though from what I read).  With stock, it takes 
~8m30s... this scheduler adds a full minute.

The window wave test with a make -j5 bzImage running (fits easily in ram) 
is pretty ragged.

Ending on a more positive note, vmstat output from the parallel build looks 
quite nice.

	-Mike


  reply	other threads:[~2003-03-11  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  0:30 Jim Houston
2003-03-11  9:46 ` Mike Galbraith [this message]
2003-03-11 19:05   ` Jim Houston
2003-03-11 20:09     ` Mike Galbraith
2003-03-11 19:17   ` Mike Galbraith
2003-03-11 23:04 Jim Houston
2003-03-12  4:51 ` Mike Galbraith
2003-03-12  5:19 ` Mike Galbraith

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=5.2.0.9.2.20030311095954.01f9a008@pop.gmx.net \
    --to=efault@gmx.de \
    --cc=jim.houston@attbi.com \
    --cc=jim.houston@ccur.com \
    --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

all inboxes | Powered by JetHome®