From: Martin Knoblauch <spamtrap@knobisoft.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Understanding I/O behaviour
Date: Fri, 6 Jul 2007 03:11:53 -0700 (PDT) [thread overview]
Message-ID: <197707.68164.qm@web32604.mail.mud.yahoo.com> (raw)
In-Reply-To: <468D832B.4060002@shaw.ca>
--- Robert Hancock <hancockr@shaw.ca> wrote:
>
> Try playing with reducing /proc/sys/vm/dirty_ratio and see how that
> helps. This workload will fill up memory with dirty data very
> quickly,
> and it seems like system responsiveness often goes down the toilet
> when
> this happens and the system is going crazy trying to write it all
> out.
>
Definitely the "going crazy" part is the worst problem I see with 2.6
based kernels (late 2.4 was really better in this corner case).
I am just now playing with dirty_ratio. Anybody knows what the lower
limit is? "0" seems acceptabel, but does it actually imply "write out
immediatelly"?
Another problem, the VM parameters are not really well dociúmented in
their behaviour and interdependence.
Cheers
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
next prev parent reply other threads:[~2007-07-06 10:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.gAvf+r9fiPwNwNVqahYy5u1/Is0@ifi.uio.no>
2007-07-05 23:47 ` Understanding I/O behaviour Robert Hancock
2007-07-05 23:53 ` Jesper Juhl
2007-07-06 7:54 ` Martin Knoblauch
2007-07-06 10:15 ` Brice Figureau
2007-07-06 10:11 ` Martin Knoblauch [this message]
2007-07-07 13:23 ` Leroy van Logchem
2007-07-06 14:25 Daniel J Blueman
2007-07-06 15:17 ` Martin Knoblauch
2007-07-06 15:44 ` Daniel J Blueman
-- strict thread matches above, loose matches on Subject: below --
2007-07-06 12:44 Martin Knoblauch
2007-07-06 11:03 Martin Knoblauch
2007-07-06 10:18 Martin Knoblauch
2007-07-05 15:40 Martin Knoblauch
2007-07-05 18:15 ` Andrew Lyon
2007-07-05 20:22 ` Jesper Juhl
2007-07-08 21:28 ` Jesper Juhl
2007-07-09 8:47 ` Martin Knoblauch
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=197707.68164.qm@web32604.mail.mud.yahoo.com \
--to=spamtrap@knobisoft.de \
--cc=hancockr@shaw.ca \
--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