From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] To swap or not to swap? Is it really needed?
Date: Fri, 30 Dec 2011 00:48:18 +0200 [thread overview]
Message-ID: <20111230004818.4f40ca5d@rohan.example.com> (raw)
In-Reply-To: <CAGo3Weo10WAPosiSXy+FihBo4fmre9qcnmVq7MxWRvsG3DVNeg@mail.gmail.com>
On Thu, 29 Dec 2011 20:34:16 -0200
Claudio Roberto França Pereira <spideybr@gmail.com> wrote:
> I've run my box with 2x2GB of RAM for a while, but a couple weeks ago
> one of my chips died, and now I'm stuck with 1x2GB. That's not that
> terrible, I'm using Gentoo all day, rarely switching to Windows 7
> anyways, who really likes RAM.
> Anyway, for the last days, my machine has been really slow, with mouse
> lag, input delay, and other things. I imediately associated it to the
> lack of free RAM, but I always rushed to check the RAM usage with htop
> and it were never really high. So today I decided to turn my swap
> partition off. And the system is FLYING. I mean, it's pratically a new
> machine, now it's usable and reliable.
>
> I thought of falling back from KDE 4 to awesome (tried it earlier in
> an old notebook last year) given the memory footprint of KDE, but it
> seems that my hard disk was the culprit here.
> I've heard that Linux need a little swap partition, maybe just 512MB,
> for some tasks, but I'm not going to turn it on anytime soon. It's a
> desktop machine, 24/7, and I couldn't care less about suspend-to-disk.
>
> So, should I ban swap partitions entirely from my life? Is that ok?
This question comes up about every three months or so, and the end
result is always the same: the same people chip in with the same
answers and we all come to the same conclusion.
You should check the Gentoo archives for the most recent gigantic
thread on this, that one was particularly illuminating.
But to summarize:
You haven't given any real info for people to answer your actual
question. To do that, we need to know what exactly your machine is
doing and why, please what your swap settings are.
Generally, the kernel is happiest with a little bit of swap (512 MB is
a very much more than a little) and you can get by with that if your
apps fit into ram. KDE is reasonably smart with ram usage, if you only
have 2G it will try fit into that. If you have 22G it will try to use
lots.
If your machine was really slow, it was likely thrashing. But no-one
can say for sure - what was your disk doing at the time? What did
vmstat say was going on?
To summarize a summary, the answer to "can I ban swap?" is "maybe"
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2011-12-29 22:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 22:34 [gentoo-user] To swap or not to swap? Is it really needed? Claudio Roberto França Pereira
2011-12-29 22:48 ` Alan McKinnon [this message]
2011-12-29 23:11 ` Claudio Roberto França Pereira
2011-12-30 0:03 ` Paul Hartman
2011-12-30 2:23 ` Claudio Roberto França Pereira
2011-12-30 3:54 ` Michael Mol
2011-12-30 7:31 ` Dale
2011-12-30 13:32 ` Michael Mol
2011-12-30 14:02 ` Paul Hartman
2011-12-30 14:11 ` Peter Humphrey
2011-12-30 14:18 ` Paul Hartman
2011-12-30 14:24 ` Dale
2011-12-29 23:09 ` Dale
2011-12-30 2:56 ` [gentoo-user] " Nikos Chantziaras
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=20111230004818.4f40ca5d@rohan.example.com \
--to=alan.mckinnon@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