From: Bill Davidsen <davidsen@tmr.com>
To: kalium@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: latencies due to disk writes
Date: Tue, 27 Feb 2007 21:30:43 -0500 [thread overview]
Message-ID: <45E4E953.7060501@tmr.com> (raw)
In-Reply-To: <20070226015439.97500@gmx.net>
kalium@gmx.de wrote:
> Hello!
>
> I'm experiencing extreme lags during disk writes. I have read somewhere (didn't save the URI, sigh) that this is actually related to bad (non-existing) write io priorities (CFQ only manages file reads).
>
> I could imagine two quick, easy and probably quite effective ways to prevent such lags:
>
> 1.) don't flush buffers to disk at once more than necessary.
>
Actually, in many cases this is just what you do want, to avoid filling
memory with buffered writes and then flushing them on time or memory runout.
Investigate the /proc/sys/vm/dirty_* values.
> 2.) relate CPU niceness to max write buffer fill level (ie. the point where it gets forced to be flushed to disk -- a conservative estimate would be much better than nothing): (100-5*nicelevel)%, ie. writes for processes having nice level 19 are blocked/delayed until the write buffer is below 5%. That way, the accounting is done at a higher and probably easier to access level.
>
> Maybe I'm just talking nonsense, but nonetheless, here are my 2 cents.
>
> Best regards,
> Mark
>
> p.s. please CC me as I'm not subscribed to this list.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
prev parent reply other threads:[~2007-02-28 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 1:54 latencies due to disk writes kalium
2007-02-26 12:35 ` Frank Ch. Eigler
2007-02-26 18:07 ` Mark Stier
2007-02-28 2:30 ` Bill Davidsen [this message]
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=45E4E953.7060501@tmr.com \
--to=davidsen@tmr.com \
--cc=kalium@gmx.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