From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} SSD instead of RAID1?
Date: Thu, 30 Jul 2009 06:47:18 -0700 [thread overview]
Message-ID: <49bf44f10907300647g1493cb10yf818a8e79a307c9c@mail.gmail.com> (raw)
In-Reply-To: <200907301501.27721.alan.mckinnon@gmail.com>
>> OK, that's right. How can I find out if 4GB RAM (the current amount)
>> is enough? From what I understand of how Linux handles memory, it
>> will fill it up as quickly as possible, and then free it as necessary.
>> This makes it difficult to determine how much RAM is necessary from
>> watching top.
>
> top lies. This has been discussed here many times. All your memory tools
> essentially tell you how much memory an app is able to see into, and most of
> that memory is shared with other stuff (like libs).
>
> You can't tell how much memory an app is using in any meaningful way, you are
> not supposed to even look at it as it changes millions of times a second. What
> you are supposed to do is select an allocation algorithm that works well for
> you in practice and let the kernel do the heavy lifting.
>
> Yes, the kernel does grab as much memory as it can for buffers and cache, then
> release it on demands. All modern operating systems have done this for many
> years - Linux just doesn't try and hide that fact from you :-)
>
>> I read on this list that the kernel needs *some* swap, even just a
>> tiny amount, to function properly. Is that true? If so, do you think
>> it would be OK to put this tiny amount of swap on a cheap SSD?
>
> Not true. I have machines with zero swap and they work just fine. I am utterly
> unconcerned with out of memory conditions as whether you have swap or not,
> when virtual memory runs out, either way you have a horrible cockup that is
> hard to fix. Then there's the oom-killer that comes along, stomps all over
> everything and just makes it worse.
Sounds good. Will commenting the swap line out of /etc/fstab and
rebooting disable swap? In order to resize the root partition to
include the swap paritition, I'll have to boot to LiveCD right?
- Grant
next prev parent reply other threads:[~2009-07-30 13:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 10:46 [gentoo-user] {OT} SSD instead of RAID1? Grant
2009-07-26 16:04 ` Stroller
2009-07-27 12:44 ` Grant
2009-07-27 17:43 ` Florian Philipp
2009-07-27 18:33 ` Florian Philipp
2009-07-27 18:42 ` James Ausmus
2009-07-28 17:52 ` Grant
2009-07-28 19:01 ` Stroller
2009-07-29 15:20 ` Grant
2009-07-29 17:25 ` Florian Philipp
2009-07-30 12:17 ` Grant
2009-07-30 12:33 ` Neil Bothwick
2009-07-30 13:00 ` Grant
2009-07-30 13:01 ` Alan McKinnon
2009-07-30 13:47 ` Grant [this message]
2009-07-30 14:05 ` Alex Schuster
2009-07-30 15:45 ` Grant
2009-07-30 15:57 ` Alan McKinnon
2009-07-30 14:57 ` Alan McKinnon
2009-07-30 15:57 ` Neil Bothwick
2009-07-30 15:20 ` Peter Humphrey
2009-07-30 13:10 ` Alex Schuster
2009-07-30 14:18 ` Paul Hartman
2009-07-30 16:03 ` Grant
2009-07-30 16:07 ` Paul Hartman
2009-07-30 16:12 ` Grant
2009-07-31 16:07 ` Grant
2009-07-29 18:15 ` Neil Bothwick
2009-07-30 11:41 ` Stroller
2009-07-31 17:31 ` Grant
2009-08-03 16:00 ` Grant
2009-07-30 12:53 ` Grant
2009-07-30 11:46 ` Stroller
2009-07-29 8:12 ` Nevynxxx
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=49bf44f10907300647g1493cb10yf818a8e79a307c9c@mail.gmail.com \
--to=emailgrant@gmail.com \
--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