All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: Lee Revell <rlrevell@joe-job.com>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Schedulers benchmark - Was: [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6
Date: Fri, 19 Aug 2005 14:41:09 +1000	[thread overview]
Message-ID: <430562E5.1070208@bigpond.net.au> (raw)
In-Reply-To: <200508191341.24821.kernel@kolivas.org>

Con Kolivas wrote:
> On Fri, 19 Aug 2005 01:28 pm, Lee Revell wrote:
> 
>>On Fri, 2005-08-19 at 05:09 +0200, Michal Piotrowski wrote:
>>
>>>Hi,
>>>here are interbench v0.29 resoults:
>>
>>The X test under simulated "Compile" load looks most interesting.
>>
>>Most of the schedulers do quite poorly on this test - only Zaphod with
>>default max_ia_bonus and max_tpt_bonus manages to deliver under 100ms
>>max latency.  As expected with interactivity bonus disabled it performs
>>horribly.
> 
> 
> The compile load is not a real compile load; it is an extreme exaggeration of 
> what happens during a compile and this is done to increase the sensitivity of 
> this test. It is _not_ worth trying to get a perfect score in this.
> 
> 
>>I'd like to see some results with X reniced to -10.  Despite what the
>>2.6 release notes say, this still seems to make a difference.
> 
> 
> Well of course it helps X - but then any X load totally fscks up audio on 
> mainline and staircase which is why it's recommended not to renice it.

Maybe we could use interbench to find a nice value for X that doesn't 
destroy Audio and Video?  The results that I just posted for 
spa_no_frills with X reniced to -10 suggest that the other schedulers 
could cope with something closer to zero.

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

  reply	other threads:[~2005-08-19  4:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  4:46 [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6 Peter Williams
2005-08-15 12:29 ` Michal Piotrowski
     [not found]   ` <43012427.9080406@bigpond.net.au>
     [not found]     ` <4301330B.3070400@bigpond.net.au>
2005-08-16 12:54       ` Michal Piotrowski
2005-08-17  8:00   ` Con Kolivas
2005-08-17 11:23     ` Michal Piotrowski
2005-08-17 12:31       ` Con Kolivas
2005-08-16 21:49 ` Schedulers benchmark - Was: " Michal Piotrowski
2005-08-17  8:10   ` Peter Williams
2005-08-17  9:03     ` Con Kolivas
2005-08-17 18:04       ` Michal Piotrowski
2005-08-17 21:35         ` Con Kolivas
2005-08-17 23:15       ` Peter Williams
2005-08-17 23:16         ` Con Kolivas
2005-08-17 23:48           ` Peter Williams
2005-08-17 23:45             ` Con Kolivas
2005-08-19  3:09               ` Michal Piotrowski
2005-08-19  3:28                 ` Lee Revell
2005-08-19  3:41                   ` Con Kolivas
2005-08-19  4:41                     ` Peter Williams [this message]
2005-08-19  4:36                       ` Con Kolivas
2005-08-19 20:13                         ` Lee Revell
2005-08-20  0:31                           ` Con Kolivas
2005-08-20  3:04                             ` Lee Revell
2005-08-20 18:52                             ` Lee Revell
2005-08-19  4:26                   ` Peter Williams
2005-08-17 11:59     ` Michal Piotrowski
2005-08-21  1:34   ` Michal Piotrowski
2005-08-21  1:47     ` Con Kolivas
2005-08-21  4:16       ` Michal Piotrowski
2005-08-21  4:22         ` Con Kolivas
2005-08-21  4:44           ` Michal Piotrowski
2005-08-21  4:49             ` Con Kolivas
2005-08-21  1:37   ` Michal Piotrowski
     [not found]     ` <4309125B.4020707@bigpond.net.au>
2005-08-22 11:39       ` Michal Piotrowski

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=430562E5.1070208@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=rlrevell@joe-job.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.