From: "Wee Teck Neo" <slashboy84@msn.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Over used cache memory?
Date: Thu, 06 Nov 2003 17:33:19 +0800 [thread overview]
Message-ID: <BAY4-F16sWUjGV8NtPH00022c46@hotmail.com> (raw)
Ok...... Thanks got an idea how linux uses memory.
Thanks
----Original Message Follows----
From: Jerry Lundström <jerry.lundstrom@it.su.se>
To: Wee Teck Neo <slashboy84@msn.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: Over used cache memory?
Date: Thu, 06 Nov 2003 10:16:19 +0100
Wee Teck Neo wrote:
>But seems like the swap space is begin used because of "insufficent" free
>memory. I'm not sure if there is a performance slow down.
>
no no no, this is the way linux works. Memory from programs that are not
accessed alot are put into the swap so that the not-so-offen-used memory can
be used by other programs or the cache to speed up everything. When that
program later access the swaped memory it will load it up and remove some of
the cache and after a while it will put it back into the swap (dont have any
numbers on how long till it will but trust linux, it does it very good).
I wouldnt worry at all about those numbers, they are very common in 1gig
server systems and ive worked with alot of them, even 4gig mem systems use
the swap, thats what its for...
If you are worried about preformance with memory and such after all
configure you systems like this:
If you use IDE have the system disk on one IDE channel and a standalone swap
disk on another IDE channel (not master or slave way but ide0 or ide1). For
SCSI you can just put the swap on a seperate disk.
Doing this will speed up alot of stuff since linux have 100% access to the
swap when it needs too, it doesnt have to share the IO to the disk with
another partition.
Otherwise Id just say, dont worry about it... Linux knows what its doing...
hope it helps...
_________________________________________________________________
Keep track of Singapore & Malaysia stock prices.
http://www.msn.com.sg/money/
next reply other threads:[~2003-11-06 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 9:33 Wee Teck Neo [this message]
[not found] <BAY4-F18tJyMmxsywxZ00005d1a@hotmail.com>
2003-11-06 9:16 ` Jerry Lundström
-- strict thread matches above, loose matches on Subject: below --
2003-11-06 9:15 Wee Teck Neo
2003-11-06 19:07 ` Jose Luis Domingo Lopez
2003-11-06 19:57 ` Maciej Zenczykowski
2003-11-06 20:50 ` Daniel Gryniewicz
2003-11-06 8:05 Wee Teck Neo
2003-11-06 8:25 ` Nick Piggin
2003-11-06 8:59 ` Jerry Lundström
2003-11-06 9:11 ` Helge Hafting
2003-11-06 13:40 ` jlnance
2003-11-06 14:14 ` Gianni Tedesco
2003-11-06 21:47 ` jlnance
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=BAY4-F16sWUjGV8NtPH00022c46@hotmail.com \
--to=slashboy84@msn.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 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®