From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Swap performance
Date: Thu, 26 May 2011 19:26:20 +0200 [thread overview]
Message-ID: <201105261926.21424.wonko@wonkology.org> (raw)
Volker Armin Hemmann writes:
> On Thursday 26 May 2011 00:40:21 Alex Schuster wrote:
> > Paul Hartman writes:
> > > On Wed, May 25, 2011 at 9:20 AM, Alex Schuster <wonko@wonkology.org>
> > > wrote:
> > Maybe I should have bought 4G instead of 2G, so I'd have 10G, not 8G.
> > I'm not sure if this is recommended these days, to have one memory bank
> > with 4G and 3 others with 2G each.
>
> It is very much not recommended nor wise.
>
> Sometimes it works great, sometimes it just works, sometimes it burns
> down your village, rapes your cattle and steals your dad.
Ookay.
> > It's growing: 1405m VIRT, 851m RES, 6m SHR. Strange, I did not actually
> > use the desktop after I wrote the mail you replied to, currently I'm
> > logged in from remote.
>
> and you know that those numbers are pretty much meaningless?
Are they? Well, apparently _something_ in kwin was using hundreds of
megabytes. When I was back at the PC, I had to wait three minutes until he
password dialog appeared so I could unlock the session. iotop showed the
kwin process swapping, and no other activity.
Now kwin is at 37M, which is much lower than I thought... whoops, I made a
mistake in my previous posting, I got the virtual memory column instead by
misusing awk. I also confused kwin with plasma-desktop, which had been
really high in the past.
> about swap:
>
> 8gb ram, 24gb swap here. Swap so huge because of historical reasons
> (started with one disk with 8gb, now there are three...). But not so
> bad, considering all those tempfs mounts that can shoved in there.
Yikes. I'd rather use the space for other stuff... no matter how large hard
drives are, mine tend to fill up so I am glad for every extra gigabyte I can
find.
> Of course I am scared about the shitstorm if that ever happens.
>
> I am using the standard scheduler, no fancy io-scheduling stuff, kernel
> 2.6.36.6 and can't complain.
I do, a lot. But it seems that the system performs okay now.
> Even after a week of uptime I only get 500mb swap. Some cruft still in
> memory for some i-dont-know-reasons shoved in the hellhole swap so it
> won't get in the way of the more important stuff. Like gwenview. Or vlc.
Yeah, that's how it should be. A little swap is okay. But in my case it felt
like important stuff was swapped out.
Wonko
next reply other threads:[~2011-05-26 17:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 17:26 Alex Schuster [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 14:20 [gentoo-user] Swap performance Alex Schuster
2011-05-25 15:31 ` Paul Hartman
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
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=201105261926.21424.wonko@wonkology.org \
--to=wonko@wonkology.org \
--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