public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Con Kolivas <conman@kolivas.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [BENCHMARK] scheduler tunables with contest - max_timeslice
Date: 18 Dec 2002 20:40:06 -0500	[thread overview]
Message-ID: <1040262005.848.102.camel@phantasy> (raw)
In-Reply-To: <1040261508.3e012184e56c4@kolivas.net>

On Wed, 2002-12-18 at 20:31, Con Kolivas wrote:

> Using the osdl (http://www.osdl.org) resources provided to me I'm running a
> series of contest benchmarks on 2.5.52-mm1 and modifying the scheduler tunables
> as provided by RML's patch. SMP used to minimise how long it will take me to do
> these. This is the first in the series and I've run a range of max_timeslices
> (default is 300ms; range 100-400):

Thanks, Con.

> I will continue to do these with some of the other scheduler tunables. I will
> need recommendations if anyone is interested in further resolution testing than
> that I'm currently doing.

Some ideas...

Try child_penalty=50,75 (default is 95%)

Try max_sleep_avg=500,1000,4000 (default is 2000ms)

Try prio_bonus_ratio=0,10,30,50 (default is 25%)

Try starvation_limit=1000 (default is 2000ms)

Some of these are just academic, although I am curious about
child_penalty and starvation_limit.  In other cases, we can assuredly
improve interactivity but we have to worry about throughput and
starvation.  Nonetheless, I am curious as to what you will find. :)

	Robert Love


      reply	other threads:[~2002-12-19  1:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  1:31 [BENCHMARK] scheduler tunables with contest - max_timeslice Con Kolivas
2002-12-19  1:40 ` Robert Love [this message]

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=1040262005.848.102.camel@phantasy \
    --to=rml@tech9.net \
    --cc=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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