public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] is multi-core really worth it?
Date: Tue, 5 Dec 2017 13:57:38 +0000	[thread overview]
Message-ID: <5A26A5D2.4050104@youngman.org.uk> (raw)
In-Reply-To: <7155996.JnYQhvlp2Z@peak>

On 05/12/17 13:07, Peter Humphrey wrote:
>> (My new system when I get it working maxes out at 64GB ram so I'll have
>> > 256GB swap and (currently) 16GB ram)

> I've halved my original 4GB swap to 2GB since it never seems to be used. I'm 
> not brave enough to do away with it altogether though.

I've just had a long thread with someone on the SUSE list who refuses to
believe that the "twice ram" rule ever existed.

This despite someone else actually describing the algorithm (from which
one can see where the rule comes from), and me pointing out that (after
Linus stripped out all the "awful" optimisation code) the early vanilla
2.4 kernels enforced this rule by crashing if you broke it.

Swap was rewritten as a result of that, but I've never heard whether the
fundamental algorithm was changed, so I still provision my systems on
the assumption it's true. Disk is cheap ... my 4TB drives cost about
£110, so that makes 128GB for swap cost, what, £3? I'll probably never
need it, but hey, at that price :-)

Cheers,
Wol


  reply	other threads:[~2017-12-05 13:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22  6:52 [gentoo-user] is multi-core really worth it? Raffaele Belardi
2017-11-22  7:21 ` R0b0t1
2017-11-22  7:26 ` Jeremi Piotrowski
2017-11-22  8:23   ` Neil Bothwick
2017-11-22  8:34   ` David Haller
2017-11-22 10:07     ` [gentoo-user] " Martin Vaeth
2017-11-22 11:26       ` David Haller
2017-11-23 22:47         ` Martin Vaeth
2017-11-22 13:12   ` [gentoo-user] " Raffaele Belardi
2017-11-22 13:23     ` J. Roeleveld
2017-11-22 14:11     ` Tsukasa Mcp_Reznor
2017-11-22 14:34       ` Wols Lists
2017-11-22 16:27         ` J. Roeleveld
2017-12-05  4:11           ` Taiidan
2017-12-05  4:17             ` R0b0t1
2017-12-05 10:09             ` Peter Humphrey
2017-12-05 10:46               ` Wols Lists
2017-12-05 11:13                 ` Raffaele Belardi
2017-12-05 11:39                   ` Mick
2017-12-05 13:07                 ` Peter Humphrey
2017-12-05 13:57                   ` Wols Lists [this message]
2017-12-05 14:13                     ` Peter Humphrey
2017-12-05 21:56               ` Neil Bothwick
2017-12-06 13:29                 ` Wols Lists
2017-12-06 15:34                   ` Alan McKinnon
2017-12-06 16:07                     ` Wols Lists
2017-12-06 23:51                       ` [gentoo-user] " Ian Zimmerman
2017-12-06 16:12                     ` [gentoo-user] " Wols Lists
2017-12-06 17:24                     ` Kai Peter
2017-11-22  7:48 ` David Haller
2017-11-22  8:32   ` J. Roeleveld
2017-11-22  8:57     ` David Haller
2017-11-22 12:16       ` Peter Humphrey
2017-11-22 16:36       ` Neil Bothwick
2017-11-28 10:07 ` [gentoo-user] " Raffaele Belardi
2017-12-01 10:39   ` J. Roeleveld

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=5A26A5D2.4050104@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gentoo-user@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