From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: What should the swap size be for 4G ram?
Date: Sat, 22 Sep 2007 22:22:40 +0200 [thread overview]
Message-ID: <200709222222.40293.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <pan.2007.09.22.17.23.41@cox.net>
On Samstag, 22. September 2007, Duncan wrote:
> FWIW I'm running the kernel 2.6.23-rcs, which of course have the new CFS
> CPU scheduler. I wasn't too happy with it originally, as it'd zero out X
> responsiveness much faster than the old scheduler did, but it has gotten
> somewhat better as the rcs have progressed. I don't think it's quite
> where the old one was yet, but if one truly wants "fair", one should
> expect to play with priorities/niceness a bit more to keep smooth X
> operation when running 200+ load average and heavy swapping. It's
> certainly reasonable now; something I couldn't have said back around rc-3
> or 4, when I was pretty unhappy with it. I guess we see how good they
> did when it releases and we see if there's any outcry on people having
> trouble with X or whatever.
two things:
I am using cfs for a long time now - since shortly after the first patches.
And everytime a new patch arrived I compared it with an unpatched kernel (at
the moment 2.6.22.5) and everytime I had the same result:
X is much, much, much and a lot better with cfs. I never had such a snappy X.
X rules with cfs. It is just great. Under load, without load, it does not
matter. cfs is better. I am really curios what I did right that you do wrong.
second:
a little bit less text would be great. This was almost TL;DR. You turned a
simple question about swapsize into a large sermon about your cool box with
it bazillion of gb ram, its superduper harddisk setup and its amazing
computing power that makes it survive a 200 load.
Back at school you would have failed the test because of missing the point.
Remember: this is an international list. Less text is almost always much more
readable. Not everybody enjoys picking the few cherries of relevant
information out of a sea of words.
Glück Auf
--
gentoo-amd64@gentoo.org mailing list
prev parent reply other threads:[~2007-09-22 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 3:16 [gentoo-amd64] What should the swap size be for 4G ram? P.V.Anthony
2007-09-22 3:22 ` P.V.Anthony
2007-09-22 15:15 ` Richard Freeman
2007-09-22 15:22 ` Volker Armin Hemmann
2007-09-22 16:24 ` B Vance
2007-09-22 17:23 ` Richard Freeman
2007-09-22 17:23 ` [gentoo-amd64] " Duncan
2007-09-22 20:22 ` Volker Armin Hemmann [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=200709222222.40293.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--cc=gentoo-amd64@lists.gentoo.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