From: kalium@gmx.de
To: linux-kernel@vger.kernel.org
Subject: latencies due to disk writes
Date: Mon, 26 Feb 2007 02:54:39 +0100 [thread overview]
Message-ID: <20070226015439.97500@gmx.net> (raw)
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.
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.
--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: www.gmx.net/de/go/mailfooter/topmail-out
next reply other threads:[~2007-02-26 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 1:54 kalium [this message]
2007-02-26 12:35 ` latencies due to disk writes Frank Ch. Eigler
2007-02-26 18:07 ` Mark Stier
2007-02-28 2:30 ` Bill Davidsen
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=20070226015439.97500@gmx.net \
--to=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