From: "Al T" <at@fiber.net>
To: linux-mm@kvack.org
Subject: Set file cache size (2.4.18)
Date: Fri, 15 Mar 2002 09:53:54 -0700 [thread overview]
Message-ID: <3C91C4B2.8458.19B077CE@localhost> (raw)
I am currently experimenting Linux on an old laptop I got cheap. It has
a max. of 24 MB of ram and an ISA IDE controller. It is an old
machine and runs quite well. I built my own Linux system to maximize
its power.
But, when I load large programs (KDE 2, for example), the system
slows down to a crawl. This is what I've been able to figure out:
- KDE 2 is a memory hog. In order to compensate for that, a lot of
swap must be used. But, with a 3 MB/sec transfer speed, it's just not
very fast.
- According to TOP, the CPU is not in heavy use. It is usually 30%
idle during the process, meaning the bottleneck is I/O.
- At the end of the process, the swap usage is ~18,00k, with ~10,000k
in buffer/cache.
- X is not a problem, since it can be loaded without using swap.
Based on this, I realized memory has been flipped around: what should
be in disk (files) is now in memory (cache), and what should be in
memory is now in disk (swap).
I remember in Windows 95 it was possible to set the minimum and
maximum values for the file cache. Tweaking these values increased
performance on low memory systems, since it would ensure large
amounts of memory were not used to cache the disk and memory
pages would not be thrown out to disk.
I've looked through /proc and on the internet for a way to change the
maximum cache size. It seems like it was available on early 2.4
kernels, but it's not in the 2.4.18 kernel.
How do I restrict the size of the cache and buffer?
@
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
reply other threads:[~2002-03-15 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C91C4B2.8458.19B077CE@localhost \
--to=at@fiber.net \
--cc=linux-mm@kvack.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