mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Robert Love <rml@tech9.net>
Subject: Re: [BENCHMARK] scheduler tunables with contest - interactive_delta
Date: Sat, 21 Dec 2002 23:40:50 +1100	[thread overview]
Message-ID: <200212212341.07504.conman@kolivas.net> (raw)
In-Reply-To: <200212211307.15666.m.c.p@wolk-project.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>On Saturday 21 December 2002 05:39, Con Kolivas wrote:
>
>Hi Con,
>
>> Seems like io_load likes lower interactive deltas (lower the better?) and
>> mem_load likes high interactive_deltas (sweet spot 5).
>
>Yes, seems so. I think this is a good thing for autoregulating 8-)

Exactly my thoughts. Increasingly as the numbers are rolling out it is clear 
the defaults seem to be pretty darn good (thanks mingo), but for -ck at least 
I wont be able to resist and will autoregulate them once I have a full set of 
numbers to play with. I'll get subsets of numbers (too messy to post them all 
here) and decide what to use for my ranges. It's my impression so far that 
the desktop experience with static numbers can only be improved upon by 
dropping the max timeslice to resemble that of the old scheduler. Perhaps a 
max timeslice of around 150ms.

Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE+BGFVF6dfvkL3i1gRAkQBAJsH5MLDRvSpa2VIY+u4Up2FZhdkUQCgg8sq
FAQx+63jqkrR1IUHIA3zZVQ=
=jWrY
-----END PGP SIGNATURE-----

      reply	other threads:[~2002-12-21 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-21  4:39 Con Kolivas
2002-12-21 12:07 ` Marc-Christian Petersen
2002-12-21 12:40   ` Con Kolivas [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=200212212341.07504.conman@kolivas.net \
    --to=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    --cc=rml@tech9.net \
    /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

Powered by JetHome