From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Swap performance
Date: Wed, 25 May 2011 10:31:19 -0500 [thread overview]
Message-ID: <BANLkTinOuL3EJ5T-+XoYiNP9vqKjV7qNGw@mail.gmail.com> (raw)
In-Reply-To: <201105251621.00659.wonko@wonkology.org>
On Wed, May 25, 2011 at 9:20 AM, Alex Schuster <wonko@wonkology.org> wrote:
> Hi there!
>
> I still wonder why my KDE4 system starts swapping so early. Until a week
> ago, I had 6G of RAM, but after a day of being logged in, I usually had some
> swap usage. Sometimes this goes up to 1.5G, this is when the system becomes
> way too slow and I log out.
I can't remember the last time my swap was used at all. I have 12G of
RAM, but in my prior system with 8G it was the same. Only in a rare
case when some program had run-away memory usage/memory leak did I
ever get to swap usage... I'm using vanilla kernel 2.6.39 with no
patches, no BFS. And I use proprietary nvidia-drivers. I normally
don't have so many programs running at once, but it happens sometimes.
Since 2.6.38 and enabling automatic process grouping, I don't use nice
or ionice at all anymore. I do parallel emerge with -j along with make
-j12 and never notice any slowdown or lag in UI at all.
With KDE4 logged in, and no GUI apps running (other than knutmon and
wicd), my RAM usage is slightly less than 900M (not counting
filesystem caches).
>BTW, does anyone else's kwin use 750M? That's pretty high, I think it used
>to be more like 300M.
My kwin (4.6.3-r1) has currently 507M VIRT, 54M RES, 37M SHR according to top.
My worst memory offenders, by resident memory:
clamd 124M
denyhosts 114M
X 75M
plasma-desktop 56M
By virtual memory:
krunner 964M
wicd-client (python) 681M
plasma-desktop 643M
kded4 581M
>Or I do a 'swapoff -a && swapon -a', this empties the swap and also
>frees memory. But this takes _quite_ _a_ _while_. Once I measured 37 minutes
>to clear 1G of swap.
My PC doesn't swap, but in my Nokia N900, it runs Linux and X, heavy
use of gtk and Qt4 libs, it has 256M of RAM and 768M of swap on eMMC
(transfer rate about 20MB/sec). It swaps like crazy. :) Usually there
is more swap in use than RAM, actually.
When I move the swap to a slow SD card instead (2MB/sec transfer
rate), even in that slow device, swapoff on the eMMC swap partition
with ~500M in-use takes about 2 or 3 minutes at most with the data
being swapped slowly into the SD card.
So I think in your case it should be much faster than that!
next prev parent reply other threads:[~2011-05-25 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 14:20 [gentoo-user] Swap performance Alex Schuster
2011-05-25 15:31 ` Paul Hartman [this message]
2011-05-25 16:58 ` Volker Armin Hemmann
2011-05-25 19:34 ` Paul Hartman
2011-05-25 20:03 ` Alan McKinnon
2011-05-25 20:38 ` Alex Schuster
2011-05-25 22:40 ` Alex Schuster
2011-05-26 16:30 ` Volker Armin Hemmann
2011-05-25 16:49 ` Alan McKinnon
2011-05-26 20:49 ` Mick
2011-05-25 16:53 ` Volker Armin Hemmann
2011-05-25 20:07 ` Alan McKinnon
2011-05-26 13:32 ` Sebastian Beßler
2011-05-25 22:18 ` Alex Schuster
-- strict thread matches above, loose matches on Subject: below --
2011-05-26 17:26 Alex Schuster
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=BANLkTinOuL3EJ5T-+XoYiNP9vqKjV7qNGw@mail.gmail.com \
--to=paul.hartman+gentoo@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