From: "Elmer Joandi" <elmer@linking.ee>
To: linux-kernel@vger.kernel.org
Subject: BUG: Memory usage, 2.4.10 meaning of "free" and cached.
Date: Tue, 9 Oct 2001 04:55:53 +0200 (EET) [thread overview]
Message-ID: <35766.10.110.0.21.1002596153.squirrel@mail.linking.sise> (raw)
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
About 1 G of RAM
Squid, mysql, bunch of other daemons and programs configured to take about 500MB(lots of
chroot boxes).
/tmp 's mounted as tmpfs
With 2.4.2-ac28(also tmpfs) there was 500MB cached(or somethimes on random occasions
lots of buffered). And swap being used, 300MB after pushing the computer to swap.
Now, with 2.4.10....
There is everything used (only 120M cached, 5M buffered) ,exept swap(10M),
When starting applications like soffice,mozilla and other hogs, the cached number
... grows...(and free degrades a bit if it is free at particular moment).
hovever, numbers of memory usage are much higher than with 2.4.2-ac28
stoping hogs gives us some free memory (looks like someone installed RAM on the fly
:) (not total of it, of course :) ) )
Now, taking a 300MB file with joe, opening it... the cached grows(probably as joe
makes temporary on tmpfs), swap usage grows minimally.
Quiting joe... free grows (but swap is still used minimally, 13M) and now there is plenty
of free and lots of cached(i.e. same amount of programs and memory used by
applications, but, compared to start, there has come about some hundred megs of free
memory from somewhere)
1. It seems that the meaning of "free" or "free+cached+buffered" in top has changed over the
time a bit ? It seems that all of cached is not reported as cached, and after stressing memory
and freeing those hidden cached there is more "free+cached+buffered" at the end of
memory-stressing programs run despite that no other programs have released any signifficant
amount of memory.
2. How to tell kernel to use swap more agressively ?
[-- Attachment #2: Type: application/octet-stream, Size: 2 bytes --]
reply other threads:[~2001-10-09 2:42 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=35766.10.110.0.21.1002596153.squirrel@mail.linking.sise \
--to=elmer@linking.ee \
--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
all inboxes | Powered by JetHome®