From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc1-np1
Date: Mon, 19 Jul 2004 17:00:14 -0400 [thread overview]
Message-ID: <cdhca9$6h8$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <40F8B7C5.9030201@yahoo.com.au>
Nick Piggin wrote:
> http://www.kerneltrap.org/~npiggin/2.6.8-rc1-np1/
>
> Now that I finally a highmem system, I've been able to make some progress
> on the memory management chaneges. Still needs more work though. Feedback
> would be nice if anyone is testing.
>
> Scheduler behaviour is generally pretty good now so I've increased the
> timeslice size to see how far I can push it. Some workloads really demand
> small timeslices though, so I've added /proc/sys/kernel/base_timeslice.
> If you have any problems with the default, please report it to me, and
> check if lowering this value helps.
>
> Things are working alright on my desktop with base_timeslice at 10000
> which corresponds to around 15-20 *second* timeslices, however I don't
> do much fancy, and it does have the problem of a newly forked CPU hog
> possibly causing a long freeze (fixable by using a smaller value for
> the first timeslice).
I think most people will find the long freeze worth avoiding, thanks for
making it easily adjustable. As I found out when I was evaluating sorts
and human interfaces that users would rather use a slower sort which
didn't have a "jackpot case" than one which was 30% faster but linear in
response. This was for 1-2sec typical response.
Just my guess.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2004-07-19 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 5:23 2.6.8-rc1-np1 Nick Piggin
2004-07-17 8:45 ` 2.6.8-rc1-np1 Felipe Alfaro Solana
2004-07-17 9:25 ` 2.6.8-rc1-np1 Nick Piggin
2004-07-17 20:52 ` 2.6.8-rc1-np1 Martin Schlemmer
2004-07-19 21:00 ` Bill Davidsen [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='cdhca9$6h8$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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