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 0.2
Date: Wed, 12 Mar 2003 20:54:27 +0100	[thread overview]
Message-ID: <5.2.0.9.2.20030312204553.00cd5068@pop.gmx.net> (raw)
In-Reply-To: <200303121529.h2CFTMv00924@linux.local>

[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]

At 10:29 AM 3/12/2003 -0500, Jim Houston wrote:

>Hi Mike, Everyone,

Greetings,

>Mike, I have made a few adjustments which I hope will make you happy.
>I changed the time_slice code so it gives larger time slices to
>processes with less than average priorities.  This makes my "make -j30"
>compile times match those of linux-2.5.64.

I only did one run, but yep, it's pretty close on my box too.

>I have some experimental code to address the irman issues.  My first
>change was to adjust the run_avg value during a synchronous wakeup.
>The idea is to average the values so that related processes priorities
>will clump together.  I also felt that the circle of processes passing
>a token are really a disguised compute bound process.  To punish this
>behavoir, I add a small amount to the run_avg of the woken process.
>You can adjust the amount with /proc/sys/sched/pipe_circle_tax.  I default
>this value to 5.  This obviously also punishes the innocent.  So the
>question is if the value is small enough can it fix the irman problem
>without breaking something else.

A value of 5 doesn't seem to be enough.  I fixed irman's parse problem so 
it can run the memory test properly and ran it with pipe_circle_tax set to 
5, 25 and 50.  The results are attached along with results from 
2.5.64.virgin and 2.5.64.bk5 for comparison.

There isn't any detectable change wrt the window wiggle test... still 
pretty choppy.

         -Mike

[-- Attachment #2: xx.txt --]
[-- Type: text/plain, Size: 1660 bytes --]

pipe_circle_tax = 5
aborted after 20 minutes

pipe_circle_tax = 25
[mikeg]:> time ./irman
Response time measurements (milliseconds) for: 2.5.64bk5sts
      Load       Max       Min       Avg Std. Dev.
      NULL     0.362     0.009     0.010     0.002
    MEMORY   250.048     0.009     0.019     1.075
   FILE_IO   749.965     0.010     0.027     2.199
   PROCESS   824.305     0.010     0.080     2.821

real    3m20.733s
user    0m52.662s
sys     0m20.981s

pipe_circle_tax = 50
[mikeg]:> time ./irman
Response time measurements (milliseconds) for: 2.5.64bk5sts
      Load       Max       Min       Avg Std. Dev.
      NULL     0.247     0.010     0.011     0.002
    MEMORY   375.001     0.009     0.020     1.244
   FILE_IO   499.987     0.009     0.032     2.483
   PROCESS   525.932     0.010     0.051     2.306

real    3m5.857s
user    0m54.828s
sys     0m21.571s

[mikeg]:> time ./irman
Response time measurements (milliseconds) for: 2.5.64.virgin
      Load       Max       Min       Avg Std. Dev.
      NULL     0.733     0.010     0.011     0.002
    MEMORY   151.308     0.010     0.017     0.969
   FILE_IO   454.016     0.010     0.027     2.718
   PROCESS  1216.848     0.010     0.049     6.411

real    2m46.591s
user    0m20.270s
sys     0m21.622s

[mikeg]:> time ./irman
Response time measurements (milliseconds) for: 2.5.64bk5
      Load       Max       Min       Avg Std. Dev.
      NULL     3.373     0.010     0.012     0.004
    MEMORY   106.042     0.011     0.023     1.090
   FILE_IO   312.046     0.011     0.047     3.297
   PROCESS   223.482     0.010     0.037     0.488

real    2m51.265s
user    0m29.902s
sys     0m23.920s

  reply	other threads:[~2003-03-12 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 15:29 Jim Houston
2003-03-12 19:54 ` Mike Galbraith [this message]
2003-03-13 16:33   ` Jim Houston

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.20030312204553.00cd5068@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®