From: Jens Axboe <jens.axboe@oracle.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kswapd continuously active
Date: Fri, 5 Feb 2010 14:12:21 +0100 [thread overview]
Message-ID: <20100205131220.GK1025@kernel.dk> (raw)
In-Reply-To: <alpine.LSU.2.01.1002051408280.23211@obet.zrqbmnf.qr>
On Fri, Feb 05 2010, Jan Engelhardt wrote:
>
> On Friday 2010-02-05 14:00, Jens Axboe wrote:
> >> >January 25 Feb-05
> >> >MemTotal: 8166752 kB 8166752
> >> >MemFree: 3243552 kB 3781776
> >> >Buffers: 207968 kB 4912
> >> >Cached: 2728216 kB 2684400
> >> >SwapCached: 0 kB 0
> >> >Active: 2203136 kB 495624
> >> >Inactive: 2152544 kB 3263136
> >> >Active(anon): 1167256 kB 488168
> >> >Inactive(anon): 252952 kB 583912
> >> >Active(file): 1035880 kB 7456
> >> >Inactive(file): 1899592 kB 2679224
> >> >Unevictable: 0 kB 0
> >> >Mlocked: 0 kB 0
> >> >SwapTotal: 0 kB 0
> >> >SwapFree: 0 kB 0
> >> >Dirty: 141624 kB 2662184
> >> >Writeback: 0 kB ..
> >>
> >> Today this happened again. So I looked at /proc/meminfo to paste today's
> >> values next to those from January. That is when I noticed the "Dirty"
> >> value - and thus I ran
> >>
> >> watch -d -n 1 'grep Dirty /proc/meminfo'
> >>
> >> What I see is that the dirty amount - a sync is currently running -
> >> only decreases with at most 400 KB/sec, often less than that.
> >
> >I'm guessing the barriers and commits are what is killing your
> >performance. What happens with barrier=0?
>
> The ext4 filesystem is already mounted with barrier=0. If there
> is any block-level barriers I also can turn off, what would be
> the command?
barrier=0 is enough. I do wonder why your writeback rate is that slow,
then. The disk has write back caching enabled?
--
Jens Axboe
next prev parent reply other threads:[~2010-02-05 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 23:52 kswapd continuously active Jan Engelhardt
2010-01-25 13:06 ` Jens Axboe
2010-01-25 13:22 ` Jan Engelhardt
2010-02-05 12:35 ` Jan Engelhardt
2010-02-05 13:00 ` Jens Axboe
2010-02-05 13:09 ` Jan Engelhardt
2010-02-05 13:12 ` Jens Axboe [this message]
2010-02-05 13:24 ` Jan Engelhardt
2010-02-07 10:50 ` Jan Engelhardt
2010-02-08 0:07 ` Jan Engelhardt
2010-02-08 14:08 ` Jens Axboe
2010-02-10 15:18 ` Jan Engelhardt
2010-02-10 15:23 ` Jan Engelhardt
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=20100205131220.GK1025@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.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