From: Sven-Haegar Koch <haegar@sdinet.de>
To: Dan Merillat <dan.merillat@gmail.com>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
preining@logic.at, riel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.31 - very swap-happy with plenty of free RAM
Date: Thu, 19 Nov 2009 02:09:09 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.00.0911190200370.32644@aurora.sdinet.de> (raw)
In-Reply-To: <c0c067900911181640h64971680l4da14cdbe9fa6d59@mail.gmail.com>
On Wed, 18 Nov 2009, Dan Merillat wrote:
> On Wed, Nov 18, 2009 at 4:45 PM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>
> > I have a pretty powerful desktop machine with 8 GB RAM, fast disks with
> > RAID-1 etc.
>
> > 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.
>
> This is the type of hefty workstation many of the core developers
> have, running similar workloads, so I'm somewhat surprised that the
> default VM settings have this kind of issue.
>
> > Do a "swapoff -a", and everything is snappy and responsive as it should,
> > there are no more lags.
>
> Yes, that's my exact finding.
>
> Is this weird IO storm happening for anyone else with plenty of memory
> (for their taskload?)
For me it happend on my laptop. 3gb RAM, and a 1gb VMWare Windows-XP
instance running, plus the usual like firefox, thunderbird, kde4.
Without running vmware it did not happen. And since I have now disabled
barriers on the xfs /home partition (on luks crypto lvm) it also does
not happen anymore.
The machine is currently 300mb in swap, together with >2gb shown by free
as cached - as I just copied 10gb around nothing I worry about.
For me when it happened it looked like when a big bunch of data is to
be commited to disk xfs seeks between superblock/journal and data
and syncs/waits between each step - reducing the write speed of the
disk from the normal >20mb/s to less than 2mb/s and also delaying all
other disk-accesses in the meantime.
c'ya
sven
ps: I know with disabling barriers I sacrifice some data safety, but
better a usable and fast system than everything ultra-safe and
slow - for safety in suche rare case there is a backup.
--
The lights are fading out, once more...
next prev parent reply other threads:[~2009-11-19 1:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 21:45 Tomasz Chmielewski
2009-11-19 0:40 ` Dan Merillat
2009-11-19 1:09 ` Sven-Haegar Koch [this message]
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=alpine.DEB.2.00.0911190200370.32644@aurora.sdinet.de \
--to=haegar@sdinet.de \
--cc=dan.merillat@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.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
all inboxes | Powered by JetHome®