From: Andi Kleen <ak@muc.de>
To: David B Harris <david@eelf.ddts.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test6 scheduler goodness
Date: Sun, 05 Oct 2003 11:50:52 +0200 [thread overview]
Message-ID: <m3n0cgau83.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <D0zL.3Ew.19@gated-at.bofh.it> (David B Harris's message of "Sat, 04 Oct 2003 21:50:10 +0200")
David B Harris <david@eelf.ddts.net> writes:
> 4) In either 2.6.0-test5, or 2.6.0-test6 (I'm using 2.6.0-test6, I
> skipped test5), responsiveness was magically fixed for my workload case.
> I still have lower throughput, apparently (big compiles and whatnot take
> about 20% longer), but I recently got a CPU upgrade so I don't
Everything CPU bound should run a few percent slower on 2.6 because
it uses HZ=1000. You could recompile with HZ=100 and see if that fixes
that (just change HZ to 100 in asm/param.h)
20% sounds a big high just for HZ degradation though.
-Andi
next parent reply other threads:[~2003-10-05 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D0zL.3Ew.19@gated-at.bofh.it>
2003-10-05 9:50 ` Andi Kleen [this message]
2003-10-04 19:17 2.6.0-test6 scheduler goodness David B Harris
2003-10-05 3:13 ` Nick Piggin
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=m3n0cgau83.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=david@eelf.ddts.net \
--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