From: Laurent Chavet <lchavet@av.com>
To: linux-kernel@vger.kernel.org
Subject: Is there a way to turn file caching off ?
Date: Tue, 17 Apr 2001 09:37:24 -0700 [thread overview]
Message-ID: <3ADC7144.36E715C5@av.com> (raw)
Hi,
I'm running on a machine with 2GB of memory and dual PIII 550MHZ.
Just after boot with "nothing else running":
I run a program that almost like dd if=/dev/null of=/local/test
count=10000 bs=1000000
Except that there is a thread for reading and a thread for writing.
The program itself almost doesn't take any CPU.
What's going on is top showing:
First cache grows to the size of RAM (2GB) with transfer rate
slowing down as the cache grows.
Then the transfer rates drops a lot (2 to 3 time slower than the
drive capacity) and there is a very high CPU usage of system time (more
than a CPU) used by bdflush and kswapd (and some others like kupdated).
Of course my real application doesn't go from /dev/zero to file but it
still only does sequential access, and it seems that I pay a high price
for the file caching when I'm not using it at all.
Is there a way to turn file caching off, or at least limit its size ?
Thanks,
Laurent Chavet
next reply other threads:[~2001-04-18 1:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 16:37 Laurent Chavet [this message]
2001-04-18 4:56 ` Is there a way to turn file caching off ? David Schwartz
2001-04-18 11:49 ` Bjorn Wesen
2001-04-18 13:43 ` Jeremy Jackson
2001-04-18 9:56 ` Very bad behavior of kswapd Laurent Chavet
2001-04-18 18:52 ` Rik van Riel
2001-04-18 19:15 ` David S. Miller
2001-04-19 8:21 ` Is there a way to turn file caching off ? Helge Hafting
2001-04-19 16:15 ` Jeremy Jackson
2001-04-19 18:01 ` John Lenton
[not found] <3ADD4E61.A2A9CE9@av.com>
2001-04-18 18:21 ` David Schwartz
2001-04-18 19:00 ` Andrea Arcangeli
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=3ADC7144.36E715C5@av.com \
--to=lchavet@av.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.