From: Bill Davidsen <davidsen@tmr.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Ciprian <cipicip@yahoo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6 speed
Date: Mon, 25 Jul 2005 15:52:20 -0400 [thread overview]
Message-ID: <42E542F4.8020808@tmr.com> (raw)
In-Reply-To: <1122245346.27064.4.camel@mindpipe>
Lee Revell wrote:
> On Sun, 2005-07-24 at 17:03 -0400, Florin Malita wrote:
>
>>the x86 timer interrupt
>>frequency has increased from 100Hz to 1KHz (it's about to be lowered
>>to 250Hz)
>
>
> This is by no means a done deal. So far no one has posted ANY evidence
> that dropping HZ to 250 helps (except one result on a atypically large
> system), and there's plenty of evidence that it doesn't.
If nothing else it does seem to make media applications unhappy under
some loads.
I personally think 1k should stay the default and let people with
special needs use the other. Nice to select at boot time, people who
need accuracy above all could use 866 (or whatever tick rate near that
was the lowest error).
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-07-25 19:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 19:12 kernel 2.6 speed Ciprian
2005-07-24 19:41 ` Brice Goglin
2005-07-24 19:47 ` Dag Nygren
2005-07-24 20:40 ` Puneet Vyas
2005-07-24 21:03 ` Florin Malita
2005-07-24 22:49 ` Lee Revell
2005-07-25 19:52 ` Bill Davidsen [this message]
2005-07-24 21:46 ` Jan Engelhardt
2005-07-24 23:47 ` Alan Cox
2005-07-25 4:10 ` Florin Malita
2005-07-25 5:18 ` Willy Tarreau
2005-07-25 6:47 ` Ciprian
2005-07-26 5:55 ` cutaway
2005-07-26 19:45 ` Florin Malita
-- strict thread matches above, loose matches on Subject: below --
2005-08-03 15:31 Henrik Holst
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=42E542F4.8020808@tmr.com \
--to=davidsen@tmr.com \
--cc=cipicip@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox