From: Gordan Bobic <gordan-UpbECiGlrmGsTnJN9+BGXg@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Cache Churn
Date: Wed, 10 Aug 2011 12:17:45 +0100 [thread overview]
Message-ID: <09449c6acbe526ffa056cf4b7d005032@mail.shatteredsilicon.net> (raw)
Another performance related problem I am seeing due to nilfs_cleanerd
is that it causes unhealthy amounts of cache churn. It's reads and
writes are buffered, which inevitably means that things it reads will
get cached. Since it is going through all the blocks on the fs that have
any garbage to collect, it will eat through all the available memory
pretty quickly. It also means that it will push out of caches things
that really should stay in caches.
Since cleanerd's actual disk I/O is going to have no correlation with
actual file access pattern, is there a way to make cleanerd always
operate with something like the O_DIRECT flag so that is's reads won't
fill up the page cache?
This is a pretty serious problem on small machines running of cheap
flash (think ARM machines with 512MB of RAM and slow flash media).
The quick and dirty workaround I am pondering at the moment is to set
up a cron job that runs once/minute, checks df, and starts/kills
nilfs_cleanerd depending on how much free space is available, but that's
not really a solution.
Gordan
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-08-10 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 11:17 Gordan Bobic [this message]
[not found] ` <09449c6acbe526ffa056cf4b7d005032-tp2ajI7sM87MEvS+BUbURm2TqnkC6wfpXqFh9Ls21Oc@public.gmane.org>
2011-08-23 5:38 ` Cache Churn Ryusuke Konishi
[not found] ` <20110823.143849.52186207.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-08-23 16:53 ` Gordan Bobic
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=09449c6acbe526ffa056cf4b7d005032@mail.shatteredsilicon.net \
--to=gordan-upbeciglrmgstnjn9+bgxg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).