linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: preining@logic.at, riel@redhat.com, dan.merillat@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.31 - very swap-happy with plenty of free RAM
Date: Wed, 18 Nov 2009 22:45:14 +0100	[thread overview]
Message-ID: <4B046AEA.80109@wpkg.org> (raw)

Norbert Preining wrote:

> So what normally trashed my system to a quasi halt I tried after a swapoff -a,
> *two* svn up of really big repositories (some Gb), plus starting 
> VirtualBox Windows XP with 1Gb virtual RAM on a 2Gb machine.
> 
> And see hoho, no problem at all. Everything remains responsive and happy.
> The memory was never above 60% in use, but 40% in cache, and all 
> without any problems.
> 
> So that seems to be a real bug.
> 
> I am running currently 2.6.32-rc7, but experienced that already in the
> 31-rc version. Hard to pinpoint exactely where it happens.

Similar here (with 2.6.31.6 kernel).

I have a pretty powerful desktop machine with 8 GB RAM, fast disks with 
RAID-1 etc.

It runs 5 (mostly idle) KVM machines, Firefox, Thunderbird, KDE4, image 
editing program, multiseat X session. Around 6 GB of RAM used when 
caches/buffers are excluded.

Every 10 minutes or so, machine is really unresponsive, load jumps to 10 
or 20. Mouse pointer jumps, it's impossible to change between windows etc.

Do a "swapoff -a", and everything is snappy and responsive as it should, 
there are no more lags.

I noticed that with swap disabled, "Dirty" (in /proc/meminfo) is way 
below 100 MB (usually, 50 MB or so).
With swap enabled, it "Dirty" is usually around 300-500-700 MB, and from 
time to time, the system basically thrashes the disks, and everything is 
unresponsive.
Similar to uncompressing a big tar archive - lots of IO, system 
unresponsive.

BTW, did you try:

echo 0 > /proc/sys/vm/swappiness
swapoff -a
swapon -a


-- 
Tomasz Chmielewski
http://wpkg.org


             reply	other threads:[~2009-11-18 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 21:45 Tomasz Chmielewski [this message]
2009-11-19  0:40 ` Linux 2.6.31 - very swap-happy with plenty of free RAM Dan Merillat
2009-11-19  1:09   ` Sven-Haegar Koch
2009-11-19  1:38     ` Dave Chinner
2009-11-19  6:43       ` Tomasz Chmielewski
2009-11-23 21:57         ` Dan Merillat
2009-11-27  1:56   ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2009-10-05  1:16 complete IO hang since a few kernel revision Norbert Preining
2009-11-18  7:56 ` Linux 2.6.31 - very swap-happy with plenty of free RAM Dan Merillat
2009-11-18 15:22   ` Rik van Riel
2009-11-18 15:48   ` Norbert Preining
2009-11-19 14:36   ` KOSAKI Motohiro
2009-11-25 23:13     ` Dan Merillat
2009-11-26  1:54       ` Rik van Riel
2009-12-03  4:16         ` Dan Merillat
2009-12-07 20:49           ` Dan Merillat
2009-12-09 20:48             ` Henrique de Moraes Holschuh
2009-12-09 21:18               ` Rik van Riel

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=4B046AEA.80109@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=dan.merillat@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    --cc=riel@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).