From: Nick Piggin <piggin@cyberone.com.au>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Nick's scheduler policy v7
Date: Tue, 26 Aug 2003 14:04:38 +1000 [thread overview]
Message-ID: <3F4ADC56.9010900@cyberone.com.au> (raw)
In-Reply-To: <3070000.1061868247@[10.10.2.4]>
Martin J. Bligh wrote:
>>I didn't miss 5 revisions, I'll just stick to using my internal
>>numbering for releases.
>>
>>This one has a few changes. Children now get a priority boost
>>on fork, and parents retain more priority after forking a child,
>>however exiting CPU hogs will now penalise parents a bit.
>>
>>Timeslice scaling was tweaked a bit. Oh and remember raising X's
>>priority should _help_ interactivity with this patch, and IMO is
>>not an unreasonable thing to be doing.
>>
>>Please test. I'm not getting enough feedback!
>>
>
>Well, it's actually a bit faster than either mainline or your previous
>rev whilst running SDET:
>
>SDET 128 (see disclaimer)
> Throughput Std. Dev
> 2.6.0-test4 100.0% 0.3%
> 2.6.0-test4-nick 102.9% 0.3%
> 2.6.0-test4-nick7a 105.1% 0.5%
>
>But kernbench is significantly slower. The increase in sys time has
>dropped from last time, but user time is up.
>
>Kernbench: (make -j vmlinux, maximal tasks)
> Elapsed System User CPU
> 2.6.0-test4 45.87 116.92 571.10 1499.00
> 2.6.0-test4-nick 49.37 131.31 611.15 1500.75
> 2.6.0-test4-nick7a 49.48 125.95 617.71 1502.00
>
Thanks Martin. OK, so the drop in kernbench is quite likely to be what
I thought - elevated priorities (caused by eg. make waiting for children)
causing timeslices to shrink. As long as its not a fundamental problem,
this should be able to be tweaked back.
Yeah, I guess the random kernel and user times are probably due to cache.
next prev parent reply other threads:[~2003-08-26 4:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 12:35 [PATCH] Nick's scheduler policy Nick Piggin
2003-08-24 14:29 ` Felipe Alfaro Solana
2003-08-25 3:05 ` Nick Piggin
2003-08-25 22:30 ` Bill Davidsen
2003-08-24 16:55 ` Martin J. Bligh
2003-08-25 3:00 ` Nick Piggin
2003-08-25 10:41 ` [PATCH] Nick's scheduler policy v7 Nick Piggin
2003-08-25 11:03 ` Felipe Alfaro Solana
2003-08-25 14:36 ` Måns Rullgård
2003-08-26 3:24 ` Martin J. Bligh
2003-08-26 4:04 ` Nick Piggin [this message]
2003-08-26 9:44 ` Yaroslav Rastrigin
2003-08-27 9:28 ` Mike Galbraith
2003-08-25 3:27 ` [PATCH] Nick's scheduler policy Randy.Dunlap
2003-08-25 3:36 ` Nick Piggin
2003-08-26 3:16 ` Mike Fedyk
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=3F4ADC56.9010900@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).